a1doors1
asked on
Reverse DNS entries for MX records
Experts,
When I go to dnsreport.com I get this error about reverse dns records:
RROR: The IP of one or more of your mail server(s) have no reverse DNS (PTR) entries/* (if you see "Timeout" below, it may mean that your DNS servers did not respond fast enough)*/. RFC1912 2.1 says you should have a reverse DNS for all your mail servers. It is strongly urged that you have them, as many mailservers will not accept mail from mailservers with no reverse DNS entry. You can double-check using the 'Reverse DNS Lookup' tool at the DNSstuff site if you recently changed your reverse DNS entry (it contacts your servers in real time; the reverse DNS lookups in the DNS report use our local caching DNS server). The problem MX records are: 205.89.66.64.in-addr.arpa [No reverse DNS entry (rcode: 3 ancount: 0) (check it)]
How do I go about fixing this?
When I go to dnsreport.com I get this error about reverse dns records:
RROR: The IP of one or more of your mail server(s) have no reverse DNS (PTR) entries/* (if you see "Timeout" below, it may mean that your DNS servers did not respond fast enough)*/. RFC1912 2.1 says you should have a reverse DNS for all your mail servers. It is strongly urged that you have them, as many mailservers will not accept mail from mailservers with no reverse DNS entry. You can double-check using the 'Reverse DNS Lookup' tool at the DNSstuff site if you recently changed your reverse DNS entry (it contacts your servers in real time; the reverse DNS lookups in the DNS report use our local caching DNS server). The problem MX records are: 205.89.66.64.in-addr.arpa [No reverse DNS entry (rcode: 3 ancount: 0) (check it)]
How do I go about fixing this?
ASKER
Where do I go to resolve this? Godaddy.com or my ISP? When I go to dnsreports.com I get this:
MYDOMAIN.COM is not an IP address, so I am using 64.66.89.2 (the A record for MYDOMAIN.COM).
Location: United States [City: Wichita, Kansas]
Preparation:
The reverse DNS entry for an IP is found by reversing the IP, adding it to "in-addr.arpa", and looking up the PTR record.
So, the reverse DNS entry for 64.66.89.2 is found by looking up the PTR record for
205.89.66.64.in-addr.arpa.
All DNS requests start by asking the root servers, and they let us know what to do next.
See How Reverse DNS Lookups Work for more information.
How I am searching:
Asking e.root-servers.net for 205.89.66.64.in-addr.arpa PTR record:
e.root-servers.net says to go to chia.arin.net. (zone: 64.in-addr.arpa.)
Asking chia.arin.net. for 205.89.66.64.in-addr.arpa PTR record:
chia.arin.net [192.5.6.32] says to go to ns3.telcove.net. (zone: 89.66.64.in-addr.arpa.)
Asking ns3.telcove.net. for 205.89.66.64.in-addr.arpa PTR record: Reports that no PTR records exist [from 24.56.100.11].
Answer:
No PTR records exist for 64.66.89.2. [Neg TTL=43200 seconds]
Details:
ns3.telcove.net. (an authoritative nameserver for 89.66.64.in-addr.arpa., which is in charge of the reverse DNS for 64.66.89.2)
says that there are no PTR records for 64.66.89.2.
To get reverse DNS set up for 64.66.89.2, you need to speak to your Internet provider. You could also
check with hostmaster@telcove.net., who is in charge of the 89.66.64.in-addr.arpa. zone.
Note that all Internet accessible hosts are expected to have a reverse DNS entry (per RFC1912 2.1),
and many mailservers (such as AOL) will likely block E-mail from mailservers with no reverse DNS entry.
To see the reverse DNS traversal, to make sure that all DNS servers are reporting the correct results, you can Click Here.
MYDOMAIN.COM is not an IP address, so I am using 64.66.89.2 (the A record for MYDOMAIN.COM).
Location: United States [City: Wichita, Kansas]
Preparation:
The reverse DNS entry for an IP is found by reversing the IP, adding it to "in-addr.arpa", and looking up the PTR record.
So, the reverse DNS entry for 64.66.89.2 is found by looking up the PTR record for
205.89.66.64.in-addr.arpa.
All DNS requests start by asking the root servers, and they let us know what to do next.
See How Reverse DNS Lookups Work for more information.
How I am searching:
Asking e.root-servers.net for 205.89.66.64.in-addr.arpa PTR record:
e.root-servers.net says to go to chia.arin.net. (zone: 64.in-addr.arpa.)
Asking chia.arin.net. for 205.89.66.64.in-addr.arpa PTR record:
chia.arin.net [192.5.6.32] says to go to ns3.telcove.net. (zone: 89.66.64.in-addr.arpa.)
Asking ns3.telcove.net. for 205.89.66.64.in-addr.arpa PTR record: Reports that no PTR records exist [from 24.56.100.11].
Answer:
No PTR records exist for 64.66.89.2. [Neg TTL=43200 seconds]
Details:
ns3.telcove.net. (an authoritative nameserver for 89.66.64.in-addr.arpa., which is in charge of the reverse DNS for 64.66.89.2)
says that there are no PTR records for 64.66.89.2.
To get reverse DNS set up for 64.66.89.2, you need to speak to your Internet provider. You could also
check with hostmaster@telcove.net., who is in charge of the 89.66.64.in-addr.arpa. zone.
Note that all Internet accessible hosts are expected to have a reverse DNS entry (per RFC1912 2.1),
and many mailservers (such as AOL) will likely block E-mail from mailservers with no reverse DNS entry.
To see the reverse DNS traversal, to make sure that all DNS servers are reporting the correct results, you can Click Here.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Much appreciated!
This link also talks about RDNS:
http://amset.info/exchange/dnsconfig.asp
Thanks again to Sembee for the documentation.