RDNS LOOPING

I can't get my ISP to fix or even acknowledge this problem. One of his
servers properly refers to my DNS for a reverse lookup and the other does
not. Can anyone shed light on this. I have conclusively proved this using
the tools on dnsstuff.com:

Good Lookup:
Asking i.root-servers.net for 1.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 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: Reports
gw01-nashua.einfosystems.net. [from 204.8.44.12]

Bad Lookup:
Asking d.root-servers.net for 2.87.14.204.in-addr.arpa PTR record:
d.root-servers.net says to go to figwort.arin.net. (zone:
204.in-addr.arpa.)
Asking figwort.arin.net. for 2.87.14.204.in-addr.arpa PTR record:
figwort.arin.net [192.42.93.32] says to go to ns1.dyni.net. (zone:
87.14.204.in-addr.arpa.)
Asking ns1.dyni.net. for 2.87.14.204.in-addr.arpa PTR record:
ns1.dyni.net [204.8.44.11] says to go to D.ROOT-SERVERS.NET. (zone:
arpa.)
Asking D.ROOT-SERVERS.NET. for 2.87.14.204.in-addr.arpa PTR record:
d.root-servers.net [128.8.10.90] says to go to chia.ARIN.NET. (zone:
204.in-addr.arpa.)
Asking chia.ARIN.NET. for 2.87.14.204.in-addr.arpa PTR record:
chia.arin.net [192.5.6.32] says to go to ns1.dyni.net. (zone:
87.14.204.in-addr.arpa.)
Asking ns1.dyni.net. for 2.87.14.204.in-addr.arpa PTR record:
ns1.dyni.net [204.8.44.11] says to go to H.ROOT-SERVERS.NET. (zone:
arpa.)
Asking H.ROOT-SERVERS.NET. for 2.87.14.204.in-addr.arpa PTR record:
h.root-servers.net [128.63.2.53] says to go to dill.ARIN.NET. (zone:
204.in-addr.arpa.)
Asking dill.ARIN.NET. for 2.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.)
....

This goes on until either the query times out or one of the ARIN server
refers back to NS2 - then the query succeeds. I AM NOT a DNS expert, the ISP
IS and he cannot infer anything from this data. Am I in error assuming that
ns1.dyni.net is misconfigured?

Thanks,

John


.

Relevant Pages

  • Re: Disappearing DNS PTR entry
    ... It needs to be in your public DNS records and is usually created by the ISP who supplies your IP addresses, but could also be done whereever you site is hosted. ... I have a PTR record that disappears from the RDNS lookup. ...
    (microsoft.public.windows.server.sbs)
  • Re: Disappearing DNS PTR entry
    ... Are you trying to create the PTR record in your own SBS DNS record? ... I have a PTR record that disappears from the RDNS lookup. ... I have seen a couple articles with this exact problem but it wasn’t ...
    (microsoft.public.windows.server.sbs)
  • Reverse Lookup Zone record problem
    ... 1.It contains multiple PTR record. ... In the Forward Lookup Zone: ... Server OS: SBS2003 SP1 ...
    (microsoft.public.windows.server.sbs)
  • Re: Can not delete a PTR record
    ... Even if you set DNS to listen to one, the multihomed DC will register duplicate records in DNS, such as the LdapIpAdress and GcIpAddress records, which will cause problems with client access, group policies, DFS, etc. ... A static A record was created on DNS with the corresponding PTR record. ... Is the Reverse Zone a secondary zone, ... Are there any secondaries of this zone that another machine, possibly with the LOIS name is using, which wuold send DNS updates to it? ...
    (microsoft.public.windows.server.dns)
  • Re: Reverse DNS Issue
    ... > We currently host our own external DNS server with the ... > cannot do a Reverse DNS lookup on our domain. ... etc but can only have ONE PTR record ...
    (microsoft.public.win2000.dns)