You have total delegation screw up, the root-servers say your ns are:

VirusGate# dig @a.root-servers.net 1kom.net ns

; <<>> DiG 8.3 <<>> @a.root-servers.net 1kom.net ns ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6 ;; flags: qr rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2 ;; QUERY SECTION: ;; 1kom.net, type = NS, class = IN

;; ANSWER SECTION: 1kom.net. 2D IN NS DNS2.1kom.net. 1kom.net. 2D IN NS DNS1.1kom.net.

but your NS's say you NS's are:

VirusGate# dig @DNS2.1kom.net 1kom.net ns

; <<>> DiG 8.3 <<>> @DNS2.1kom.net 1kom.net ns ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; QUERY SECTION: ;; 1kom.net, type = NS, class = IN

;; ANSWER SECTION: 1kom.net. 1H IN NS ns1.genuity.net.

but when we ask there:

VirusGate# dig @ns1.genuity.net 1kom.net any

; <<>> DiG 8.3 <<>> @ns1.genuity.net 1kom.net any ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 12, ADDITIONAL: 12 ;; QUERY SECTION: ;; 1kom.net, type = ANY, class = IN

;; AUTHORITY SECTION: net. 4d19m9s IN NS A.ROOT-SERVERS.net. net. 4d19m9s IN NS E.GTLD-SERVERS.net. net. 4d19m9s IN NS F.GTLD-SERVERS.net. net. 4d19m9s IN NS J.GTLD-SERVERS.net. net. 4d19m9s IN NS K.GTLD-SERVERS.net. net. 4d19m9s IN NS A.GTLD-SERVERS.net. net. 4d19m9s IN NS M.GTLD-SERVERS.net. net. 4d19m9s IN NS G.GTLD-SERVERS.net. net. 4d19m9s IN NS C.GTLD-SERVERS.net. net. 4d19m9s IN NS I.GTLD-SERVERS.net. net. 4d19m9s IN NS B.GTLD-SERVERS.net. net. 4d19m9s IN NS D.GTLD-SERVERS.net.

ns1.genuity.net doesn't answer for your zone and refers us to the root-servers.

So when you say "my" do you mean DNS1.1kom.net or ns1.genuity.net?

>When I relay through another domain (which works), I am hosting the DNS >record for that domain too, and >it is identical to the one above: > >; Zone records >; > >@ A 216.184.181.211 >customer A 216.184.181.211 >dev A 216.216.179.140 >mail A 216.184.181.211 > MX 10 mail >www A 192.41.48.99

Where are the NS records?? AOL does DSN validations and where your messed up delegation, you're not helping AOL validate your domain in DNS.

>As you see, if there is a mistake for 1KOM's DNS, same mistake is done for >the relay server. I doubt this is the cause,

no, probably not.

> What I mean is, of AOL is checking for some sort of validity,

They do, and your DNS is a wrong.

> both DNS records are the same, or contain the same mistake. In any case, the MX >problem (if any) will only affect the incoming mail.

We don't know what AOL is checking, but you need to fix your delegation.

Len

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