|
Question : DNS and Reverse DNS setup! PLEASE HELP! AOL MAIL PROBLEMS!
|
|
Hi,
Can someone please help me with DNS and Reverse DNS setup so that ISP's like AOL will accept mail from my mail server? The DNS is working correctly (I think) but I cannot get the reverse DNS to work.
My ISP has delegated to me the IP addresses: 1.2.3.4 to 1.2.3.8 They suggested that I should have my PTR point to 1.2.3.3 since thats where my IP block is starting.
Below is how I have it setup:
Nameserver1: myservername.domain.com (1.2.3.4) (my external public IP) Nameserver2: ns1.swbell.net (151.164.1.1) (my ISP backup IP) - The above nameserver settings are on the directNIC domain name setup records.
Below is how I have forward DNS lookup setup for my domain name.
FORWARD LOOK UP ZONE:
SOA myservername.domain.com
NS myservername.domain.com 192.168.1.21 (my internal server IP)
NS ns1.swbell.net 151.164.1.1 (my ISP server IP) - zone transfers allowed for above servers
A Host: [same as parent folder] FQDN: mydomain.com IP: 192.168.1.21 (my internal server IP)
A Host: mail FQDN: mail.mydomain.com IP: 1.2.3.4 (my external public IP)
A Host: www FQDN: www.mydomain.com IP: 192. 168.1.21 (my internal server IP)
MX Host: myservername FQDN: myservername.domain.com
Below is how I have reverse lookup setup:
REVERSE LOOKUP ZONE:
1.2.3.x Subnet (my external IP address)
NS myservername.domain.com 192.168.1.21 (my internal server IP)
NS ns1.swbell.net 151.164.1.1
- zone transfers allowed for above servers
PTR FQDN: 3.3.2.1.in-addr.arpa hostname: mail.mydomain.com
PTR FQDN: 3.3.2.1.in-addr.arpa hostname: myservername.domain.com
Can someone please check the way I have forward and reverse lookup zones setup and tell me where I am going wrong? Do I need a CNAME record or anything else?
Thanks!
|
Answer : DNS and Reverse DNS setup! PLEASE HELP! AOL MAIL PROBLEMS!
|
|
Sorry, two hour commute home tonight. I've been reading and I haven't come up with anything else that might be at issue. While it is certainly odd that you have nameserver conflicts, I don't know that that's what's causing the problems. The reverse DNS lookup fails at your server, not at one of the higher nameservers. But if you do an nslookup from your server (which is now answering requests) you can get all of the right information. Hrmm. I'll keep thinking about this though.
|
|
|