Thanks for checking, but I am confused: Here is my DNS file for 1kom (it has an MX record):

; ; Zone records ;

@ A 216.216.179.130 dev A 216.216.179.154 localhost A 127.0.0.1 mail A 216.216.179.130 MX 0 mail pop A 216.216.179.130 server A 216.216.179.130 smtp A 216.216.179.130 www A 216.216.179.176

You are right about the NS record, I have one, but let me tell you one more strange thing:

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

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, since the relay server can send mail to AOL. What I mean is, of AOL is checking for some sort of validity, 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.

Thanks,

Omer

----- Original Message ----- From: "Len Conrad" <LConrad@Go2France.com> To: <IMail_Forum@list.ipswitch.com> Sent: Thursday, December 28, 2000 11:21 PM Subject: Re: [IMail Forum] iMail Server to AOL, part II

> > >My normal machine is 216.216.179.130, and the primary domain is 1kom.net > >The test machine is 216.216.179.140 and the primary and only domain is > >turkiye.net > > > >You can dig the DNSs if you wish. dns1.1kom.net (216.216.179.130) > > 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 > > > > > > > >