Reverse DNS

[Kevin D. Goodknecht [MVP]]

In Bryan Martin <[email protected]> posted a question
Then Kevin replied below:
: I am having a problem with some servers showing no reverse DNS. I
: have check and queried against my name servers and all report a
: correct reverse entry. Can anyone point what I may be missing.
:
: Domain:> www.ahwayside.com
: MX:> mail.ahwayside.com
: Reverse DNS:> 64.90.19.49 = mail.ahwayside.com
:
: Bryan Martin

Asking ns1.newsouth.net. for 49.19.90.64.in-addr.arpa PTR record: Timed
out. Trying again.
Asking ns1.newsouth.net. for 49.19.90.64.in-addr.arpa PTR record:
ns1.newsouth.net says to go to ns1.myplaceinspace.com. (zone:
49.19.90.64.in-addr.arpa.)
Asking ns1.myplaceinspace.com. for 49.19.90.64.in-addr.arpa PTR record:
Reports mail.ahwayside.com.

Answer:
64.90.19.49 PTR record: mail.ahwayside.com. [TTL 3600s] [A=64.90.19.49]

Asking ns2.newsouth.net. for 49.19.90.64.in-addr.arpa PTR record:
ns2.newsouth.net says to go to ns1.myplaceinspace.com. (zone:
49.19.90.64.in-addr.arpa.)
Asking ns1.myplaceinspace.com. for 49.19.90.64.in-addr.arpa PTR record:
Reports mail.ahwayside.com.

Answer:
64.90.19.49 PTR record: mail.ahwayside.com. [TTL 3600s] [A=64.90.19.49]

It looks like everything is in place.

 

[Bryan Martin]

Any ideas why we are having problems with some locations/MTAs reporting no
reverse DNS? for instance http://remote.12dt.com/rns/ or
http://www.dnsreport.com/tools/dnsreport.ch?domain=ahwayside.com .
Outgoing mail to some MTA (aol.com, yahoo.com etc...) have been queued since
mid last week with the servers reporting no reverse lookup. Dnsstuff.com
has reported the correct reverse dns the whole time so whats the deal?

Bryan Martin

 

[Jonathan de Boyne Pollard]

BM> I am having a problem with some servers showing no reverse DNS.
BM> I have check and queried against my name servers and all report
BM> a correct reverse entry.

No, they don't.

[C:\]dnsgetns 49.19.90.64.in-addr.arpa. | uniq /g
64.90.19.58
[C:\]dnsqry /serverip:64.90.19.58 ptr 49.19.90.64.in-addr.arpa.
[0.0.0.0:0000] -> [64.90.19.58:0035] 42
Header: 0000 1+0+0+0, Q, , query, no_error
Question: 49.19.90.64.in-addr.arpa. IN PTR

[64.90.19.58:0035] -> [0.0.0.0:0000] 74
Header: 0000 1+1+0+0, R, RA|AUTH, query, no_error
Question: 49.19.90.64.in-addr.arpa. IN PTR
Answer: . IN PTR 3600 mail.ahwayside.com.

[C:\]

The content DNS server at 64.90.19.58 is giving an answer that
is completely unrelated to the question being asked. It appears
to be broken. What software is it running ?

 

[Bryan Martin]

I am having a problem with some servers showing no reverse DNS. I have
check and queried against my name servers and all report a correct reverse
entry. Can anyone point what I may be missing.

Domain:> www.ahwayside.com
MX:> mail.ahwayside.com
Reverse DNS:> 64.90.19.49 = mail.ahwayside.com

Bryan Martin

 

[John Doe]

All servers are win2k advanced running sp4. Pardon my ignorance but I dont
see what your saying in the information you attached. I see what appears to
be a query for the ptr to the ip then I see an answer with the correct host
being returned. What did I miss?

 

[Kevin D. Goodknecht [MVP]]

In Bryan Martin <[email protected]> posted a question
Then Kevin replied below:
: Any ideas why we are having problems with some locations/MTAs
: reporting no reverse DNS? for instance http://remote.12dt.com/rns/ or
: http://www.dnsreport.com/tools/dnsreport.ch?domain=ahwayside.com .
: Outgoing mail to some MTA (aol.com, yahoo.com etc...) have been
: queued since mid last week with the servers reporting no reverse
: lookup. Dnsstuff.com has reported the correct reverse dns the whole
: time so whats the deal?
:
:Apparently the servers that hold the reverse lookup are not responding
quickly enough. It doesn't help that all of your records have a 0 TTL. Your
records won't get cached so every query must come from your DNS server. I
would suggest you increase the TTL on all your records, so every query
doesn't have to hit your DNS server. Your NS records won't get cached, your
"A" records won't get cached, and your MX record won't get cached, this
just adds extra load on your DNS and it is slowing your response time
considerably. You should consider raising the TTL on your NS records to at
least two days, your MX record to two days, and your "A" records to at least
1 hour.
Your SOA record is 1 hour but every thing else seems to be 0 take a look.

ahwayside.com any

NetDig 1.9
opcode: QUERY, status: NOERROR, id: 23
flags: qr aa rd ra; QUERY: 1, ANSWER: 9, AUTHORITY: 0, ADDITIONAL: 6

QUESTION SECTION:
ahwayside.com. IN ANY

ANSWER SECTION:
ahwayside.com. 0 IN A 64.90.19.49
ahwayside.com. 0 IN NS ns4.myplaceinspace.com.
ahwayside.com. 0 IN NS ns3.myplaceinspace.com.
ahwayside.com. 0 IN NS mainserver.ahwayside.com.
ahwayside.com. 0 IN NS ns2.myplaceinspace.com.
ahwayside.com. 0 IN NS ns1.myplaceinspace.com.
ahwayside.com. 3600 IN SOA mainserver.ahwayside.com.
postmaster.ahwayside.com. 1751 900 600 86400 3600
ahwayside.com. 0 IN MX 10 mail.ahwayside.com.
ahwayside.com. 0 IN Unknown RR.
RData:0x0000000000...

ADDITIONAL SECTION:
ns4.myplaceinspace.com. 0 IN A 64.90.29.190
ns3.myplaceinspace.com. 0 IN A 64.90.29.189
mainserver.ahwayside.com. 0 IN A 64.90.19.49
ns2.myplaceinspace.com. 0 IN A 64.90.19.59
ns1.myplaceinspace.com. 0 IN A 64.90.19.58
mail.ahwayside.com. 0 IN A 64.90.19.49

Query time: 90.1467 ms
Server : 64.90.19.58:53 (64.90.19.58)
When : 2/4/2004 7:57:39 AM
Size rcvd : 355