Nothing too weird about the serious DNS pb's you have, including no MX record:

o There is just one NS record in the zone The zone contains just one NS record. Every zone should contain two or more NS records, and the NS records in the zone should match the delegation data for the domain.

Errors ---------------------------------------------------------------------- o The name server "dns2.1kom.net." is only listed in delegation data The server "dns2.1kom.net." is listed as being authoritative for the zone according to the delegation data, but there is no NS record for that server in the zone data. Delegation data and zone data should always match.

o The name server "dns1.1kom.net." is only listed in delegation data The server "dns1.1kom.net." is listed as being authoritative for the zone according to the delegation data, but there is no NS record for that server in the zone data. Delegation data and zone data should always match.

o Non-authoritative data received from the server "ns1.genuity.net." The server "ns1.genuity.net." is listed as being authoritative for the domain, but it does not contain authoritative data for it.

o The name server "dns2.1kom.net." is vulnerable to spoofing attacks The cache of the server "dns2.1kom.net." can be poisoned with false data. This is a threat to the security of your domain.

o The name server "dns1.1kom.net." is vulnerable to spoofing attacks The cache of the server "dns1.1kom.net." can be poisoned with false data. This is a threat to the security of your domain.

o There are no MX records in the zone The zone contains no MX records. This will cause delivery problems for mail sent to a user in this zone. Every zone should contain at least one MX record for successful mail delivery.

http://BIND8NT.MEIway.com : Binary for ISC BIND 8.2.3 T9B for NT4 & W2K http://IMGate.MEIway.com : Build free, hi-perf, anti-spam mail gateways