Re: RDNS LOOPING
- From: "msnews.microsoft.com" <support@xxxxxxxxxxxxxxxx>
- Date: Wed, 24 Aug 2005 22:20:14 -0400
"Kevin D. Goodknecht Sr. [MVP]" <admin@xxxxxxxxxxxxxx> wrote in message
news:uKC2g0$pFHA.1096@xxxxxxxxxxxxxxxxxxxxxxx
> msnews.microsoft.com <support@xxxxxxxxxxxxxxxx> wrote:
>> 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?
>
> The authority section says this:
> AUTHORITY SECTION:
> 87.14.204.in-addr.arpa. 3557 IN NS ns1.einfosystems.net.
> 87.14.204.in-addr.arpa. 3557 IN NS ns2.einfosystems.net.
>
> Are these you two name servers?
YES
>
> Do you have this zone?
> 87.14.204.in-addr.arpa.
YES
>
> If you do then it would be my best hypothosis that the referring server
> times out before it can can get the answer from your DNS servers. So it
> goes
> back to the root and starts the lookup again.
If my server(s) was at fault, wouldn't referrals from both dyni.net
nameservers fail? Only NS2 fails and NS1 succeeds every time.
http://www.dnsstuff.com/tools/ptr.ch?ip=204.14.87.102 hit refresh and watch
>
> I'm not sure if it will work or not, but you can try adding these NS
> records
> to your 87.14.204.in-addr.arpa zone. and leave yours as the SOA Primary,
> and
> allow Zone transfers to these servers.
> ns1.dyni.net [204.8.44.11]
> ns2.dyni.net [204.8.44.12]
>
> You will probably know within a few hours if it works or not, it won't
> hurt
> the delegation, and if you don't see an improvement, you simply just
> remove
> the NS records.
>
>
> I assume this is a straight delegation instead of a Cname delegation,
> which
> is how most reverse delegations work. A straight delegation cannot be
> cached
> like a Cname delegation can, which is why most reverse delegations use the
> Cname delegation method.
> Had your ISP set up a Cname delegation you probably wouldn't have this
> problem. But Cname delegations require extra work to set up.
> Here is an example of how to configure a CName reverse delegation:
> 174419 - HOWTO Configure a Subnetted Reverse Lookup Zone on Windows NT,
> Windows 2000, or Windows Server 2003:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;174419
>
> Here is one at work:
> http://www.dnsstuff.com/tools/ptr.ch?ip=65.65.91.209
>
> This is my reverse delegation above, you will notice that most of the Time
> SBC's servers answer, this is because my server is the SOA master for the
> zone 208.91.65.65.in-addr.arpa and both of SBC's server also have a zone
> that is copied from my master.
> This type of delegation is much more reliable for reverse lookups than a
> straight delegation.
>
> Here is another type of Cname delegation that is made to a domain name,
> that
> is also very reliable:
> http://www.dnsstuff.com/tools/ptr.ch?ip=68.95.28.154
>
>
>
> --
> Best regards,
> Kevin D4 Dad Goodknecht Sr. [MVP]
> Hope This Helps
Thanks Kevin - your efforts are most appreciated.
JR
.
- References:
- RDNS LOOPING
- From: msnews.microsoft.com
- Re: RDNS LOOPING
- From: Kevin D. Goodknecht Sr. [MVP]
- RDNS LOOPING
- Prev by Date: Re: Mail server alias
- Next by Date: Re: Domain Rename
- Previous by thread: Re: RDNS LOOPING
- Next by thread: Domain Rename
- Index(es):
Relevant Pages
|
