Re: REVERSE DNS Failing

I am sorry to everyone about the long posts but I wanted to include the
output so everyone can follow along with the same data. I have put comments
between the *****'s in line.
*****
How does your service provider delegate the reverse to you? Currently I
get:
*****
[ehorley@mercury-a ehorley]$ dig @ns1.dyni.net 1.87.14.204.in-addr.arpa PTR

; <<>> DiG 9.2.1 <<>> @ns1.dyni.net 1.87.14.204.in-addr.arpa PTR
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63497
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;1.87.14.204.in-addr.arpa. IN PTR

;; ANSWER SECTION:
1.87.14.204.in-addr.arpa. 3600 IN PTR
gw01-nashua.einfosystems.net.

;; AUTHORITY SECTION:
87.14.204.in-addr.arpa. 2375 IN NS ns2.einfosystems.net.
87.14.204.in-addr.arpa. 2375 IN NS ns1.einfosystems.net.

;; ADDITIONAL SECTION:
ns1.einfosystems.net. 135254 IN A 204.14.87.11
ns2.einfosystems.net. 135254 IN A 204.14.87.3

;; Query time: 84 msec
;; SERVER: 204.8.44.11#53(ns1.dyni.net)
;; WHEN: Tue Aug 23 03:59:54 2005
;; MSG SIZE rcvd: 152

[ehorley@mercury-a ehorley]$ dig @ns2.dyni.net 1.87.14.204.in-addr.arpa PTR

; <<>> DiG 9.2.1 <<>> @ns2.dyni.net 1.87.14.204.in-addr.arpa PTR
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 7, ADDITIONAL: 6

;; QUESTION SECTION:
;1.87.14.204.in-addr.arpa. IN PTR

;; ANSWER SECTION:
1.87.14.204.in-addr.arpa. 3600 IN PTR
gw01-nashua.einfosystems.net.

;; AUTHORITY SECTION:
204.in-addr.arpa. 18076 IN NS henna.ARIN.net.
204.in-addr.arpa. 18076 IN NS indigo.ARIN.net.
204.in-addr.arpa. 18076 IN NS epazote.ARIN.net.
204.in-addr.arpa. 18076 IN NS figwort.ARIN.net.
204.in-addr.arpa. 18076 IN NS chia.ARIN.net.
204.in-addr.arpa. 18076 IN NS dill.ARIN.net.
204.in-addr.arpa. 18076 IN NS BASIL.ARIN.net.

;; ADDITIONAL SECTION:
dill.ARIN.net. 5600 IN A 192.35.51.32
BASIL.ARIN.net. 7754 IN A 192.55.83.32
henna.ARIN.net. 7754 IN A 192.26.92.32
indigo.ARIN.net. 7754 IN A 192.31.80.32
epazote.ARIN.net. 5600 IN A 192.41.162.32
figwort.ARIN.net. 5600 IN A 192.42.93.32

;; Query time: 89 msec
;; SERVER: 204.8.44.12#53(ns2.dyni.net)
;; WHEN: Tue Aug 23 04:00:01 2005
;; MSG SIZE rcvd: 328

[ehorley@mercury-a ehorley]$
*****
Notice the ns2.dyni.net server is responding back with Authorative servers
(being the top levels that handle 204.in-addr.arpa.), none of which are
einfosystems.net - this is causing your issue. However, a little while
later I got:
*****
[ehorley@mercury-a ehorley]$ dig @ns1.dyni.net 1.87.14.204.in-addr.arpa PTR

; <<>> DiG 9.2.1 <<>> @ns1.dyni.net 1.87.14.204.in-addr.arpa PTR
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52427
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;1.87.14.204.in-addr.arpa. IN PTR

;; ANSWER SECTION:
1.87.14.204.in-addr.arpa. 3334 IN PTR
gw01-nashua.einfosystems.net.

;; AUTHORITY SECTION:
87.14.204.in-addr.arpa. 2109 IN NS ns2.einfosystems.net.
87.14.204.in-addr.arpa. 2109 IN NS ns1.einfosystems.net.

;; ADDITIONAL SECTION:
ns1.einfosystems.net. 134988 IN A 204.14.87.11
ns2.einfosystems.net. 134988 IN A 204.14.87.3

;; Query time: 83 msec
;; SERVER: 204.8.44.11#53(ns1.dyni.net)
;; WHEN: Tue Aug 23 04:04:20 2005
;; MSG SIZE rcvd: 152

[ehorley@mercury-a ehorley]$ dig @ns2.dyni.net 1.87.14.204.in-addr.arpa PTR

; <<>> DiG 9.2.1 <<>> @ns2.dyni.net 1.87.14.204.in-addr.arpa PTR
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40998
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;1.87.14.204.in-addr.arpa. IN PTR

;; ANSWER SECTION:
1.87.14.204.in-addr.arpa. 3339 IN PTR
gw01-nashua.einfosystems.net.

;; AUTHORITY SECTION:
87.14.204.in-addr.arpa. 3458 IN NS ns1.einfosystems.net.
87.14.204.in-addr.arpa. 3458 IN NS ns2.einfosystems.net.

;; Query time: 81 msec
;; SERVER: 204.8.44.12#53(ns2.dyni.net)
;; WHEN: Tue Aug 23 04:04:22 2005
;; MSG SIZE rcvd: 120

[ehorley@mercury-a ehorley]$
*****
It appears that the ns2.dyni.net server is having some issues with
determining who is authoritative for the domain. This might be because
ns2.dyni.net doesn't seem to be able to resolve who ns1.einfosystems.net and
ns2.einfosystems.net are:
*****
[ehorley@mercury-a ehorley]$ dig @ns1.dyni.net 87.14.204.in-addr.arpa NS

; <<>> DiG 9.2.1 <<>> @ns1.dyni.net 87.14.204.in-addr.arpa NS
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12371
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2

;; QUESTION SECTION:
;87.14.204.in-addr.arpa. IN NS

;; ANSWER SECTION:
87.14.204.in-addr.arpa. 1595 IN NS ns2.einfosystems.net.
87.14.204.in-addr.arpa. 1595 IN NS ns1.einfosystems.net.

;; ADDITIONAL SECTION:
ns1.einfosystems.net. 134474 IN A 204.14.87.11
ns2.einfosystems.net. 134474 IN A 204.14.87.3

;; Query time: 81 msec
;; SERVER: 204.8.44.11#53(ns1.dyni.net)
;; WHEN: Tue Aug 23 04:12:54 2005
;; MSG SIZE rcvd: 124

[ehorley@mercury-a ehorley]$ dig @ns2.dyni.net 87.14.204.in-addr.arpa NS

; <<>> DiG 9.2.1 <<>> @ns2.dyni.net 87.14.204.in-addr.arpa NS
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15048
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;87.14.204.in-addr.arpa. IN NS

;; ANSWER SECTION:
87.14.204.in-addr.arpa. 2942 IN NS ns2.einfosystems.net.
87.14.204.in-addr.arpa. 2942 IN NS ns1.einfosystems.net.

;; Query time: 80 msec
;; SERVER: 204.8.44.12#53(ns2.dyni.net)
;; WHEN: Tue Aug 23 04:12:58 2005
;; MSG SIZE rcvd: 92

[ehorley@mercury-a ehorley]$
*****
Notice that the name servers are not resolved in the query against
ns2.dyni.net. Odd.
I would first look into why ns2.dyni.net cannot resolve your name servers.
Once you have that done perhaps the issue of who is authoritative for the
domain will solve itself. You will have to work with whoever manages
ns2.dyni.net to either make sure it is slaving the record correctly off of
ns1.dyni.net or that the records match completely. It doesn't appear that
it does.
It is also possible that your name servers are not published in all the top
level domain registers properly. I would check with your registrar to see
if you are in all the databases. Don't both with this until after checking
the above.
*****
Regards,
Ed Horley
Microsoft MVP Server-Networking


"msnews.microsoft.com" <support@xxxxxxxxxxxxxxxx> wrote in message
news:OmJ3gd2pFHA.2588@xxxxxxxxxxxxxxxxxxxxxxx
> This is driving me buggy - email to AOL is regularly queued up due to a
> RDNS failure. It comes and goes. I have the following from dnsstuff.com.
>
> This is how it is supposed to look:
>
> Asking i.root-servers.net for 11.87.14.204.in-addr.arpa PTR record:
> i.root-servers.net says to go to figwort.arin.net. (zone:
> 204.in-addr.arpa.)
> Asking figwort.arin.net. for 11.87.14.204.in-addr.arpa PTR record:
> figwort.arin.net [192.42.93.32] says to go to ns2.dyni.net. (zone:
> 87.14.204.in-addr.arpa.)
> Asking ns2.dyni.net. for 11.87.14.204.in-addr.arpa PTR record: Reports
> smtp.einfosystems.net. [from 204.8.44.12]
>
>
> This is what I see frequently - and in some cases the looping does not
> converge on my server:
>
> Asking c.root-servers.net for 1.87.14.204.in-addr.arpa PTR record:
> c.root-servers.net says to go to figwort.arin.net. (zone:
> 204.in-addr.arpa.)
> Asking figwort.arin.net. for 1.87.14.204.in-addr.arpa PTR record:
> figwort.arin.net [192.42.93.32] says to go to ns2.dyni.net. (zone:
> 87.14.204.in-addr.arpa.)
> Asking ns2.dyni.net. for 1.87.14.204.in-addr.arpa PTR record:
> ns2.dyni.net [204.8.44.12] says to go to epazote.ARIN.NET. (zone:
> 204.in-addr.arpa.)
> Asking epazote.ARIN.NET. for 1.87.14.204.in-addr.arpa PTR record:
> epazote.arin.net [192.41.162.32] says to go to ns2.dyni.net. (zone:
> 87.14.204.in-addr.arpa.)
> Asking ns2.dyni.net. for 1.87.14.204.in-addr.arpa PTR record:
> ns2.dyni.net [204.8.44.12] says to go to epazote.ARIN.NET. (zone:
> 204.in-addr.arpa.)
> Asking epazote.ARIN.NET. for 1.87.14.204.in-addr.arpa PTR record:
> epazote.arin.net [192.41.162.32] says to go to ns2.dyni.net. (zone:
> 87.14.204.in-addr.arpa.)
> Asking ns2.dyni.net. for 1.87.14.204.in-addr.arpa PTR record:
> ns2.dyni.net [204.8.44.12] says to go to BASIL.ARIN.NET. (zone:
> 204.in-addr.arpa.)
> Asking BASIL.ARIN.NET. for 1.87.14.204.in-addr.arpa PTR record:
> basil.arin.net [192.55.83.32] says to go to ns2.dyni.net. (zone:
> 87.14.204.in-addr.arpa.)
> Asking ns2.dyni.net. for 1.87.14.204.in-addr.arpa PTR record:
> ns2.dyni.net [204.8.44.12] says to go to chia.ARIN.NET. (zone:
> 204.in-addr.arpa.)
> Asking chia.ARIN.NET. for 1.87.14.204.in-addr.arpa PTR record:
> chia.arin.net [192.5.6.32] says to go to ns2.dyni.net. (zone:
> 87.14.204.in-addr.arpa.)
> Asking ns2.dyni.net. for 1.87.14.204.in-addr.arpa PTR record:
> ns2.dyni.net [204.8.44.12] says to go to dill.ARIN.NET. (zone:
> 204.in-addr.arpa.)
> Asking dill.ARIN.NET. for 1.87.14.204.in-addr.arpa PTR record:
> dill.arin.net [192.35.51.32] says to go to ns1.dyni.net. (zone:
> 87.14.204.in-addr.arpa.)
> Asking ns1.dyni.net. for 1.87.14.204.in-addr.arpa PTR record: Reports
> gw01-nashua.einfosystems.net. [from 204.8.44.11]
>
> Im many cases the query times out as it bounces between ns2.dyni.net and
> the various ARIN servers. I'm positive I have the reverse zone configured
> properly on my DNS server and my ISP says the same thing.
>
> jwr4
>
>
>


.

Relevant Pages

  • RE: AOL Mail Delivery
    ... I understand that your SBS server has 4 ... the mails from the other three no PTR record domain. ... Does this issue only happen when send mail to AOL? ... Right click Connectors container and click New-> SMTP connector. ...
    (microsoft.public.windows.server.sbs)
  • Re: MX Record Question
    ... day or so ago reported only one error which I believe reffers to the SBS ... boxes single dns "server Local IP" server. ... I did find the ISP's PTR record on the correced domain. ... you need to call your ISP and tell them to create a PTR ...
    (microsoft.public.windows.server.sbs)
  • Re: MX Record Question
    ... day or so ago reported only one error which I believe reffers to the SBS ... boxes single dns "server Local IP" server. ... I did find the ISP's PTR record on the correced domain. ... you need to call your ISP and tell them to create a PTR ...
    (microsoft.public.windows.server.sbs)
  • Re: DNS PTR question
    ... > Here is my setup and issue. ... > with my DNS PTR record for my domain. ... > between my intrenal network and the PIX I have an ISA 2004 server for ... These are just examples) My exchange server is ...
    (microsoft.public.win2000.dns)
  • Re: PTR how should it be set up
    ... cmd prompt from a desktop and telnet to Exchange. ... SMTP server), and in the PTR record, so that might not be reliable. ... mine points to some server at my ISP. ...
    (microsoft.public.windows.server.sbs)
Loading