 |  |
At 11:16 AM -0400 4/18/00, Scott Tudor wrote:
Re: reverse lookups
From: Men & Mice Support
Date: Wednesday, April 19, 2000
Time: 2:53:22 am
>I believe in a past email on quickDNS-talk I saw the following response:
>
>>Registering a domain file doesn't automatically give you authority over
>the reverse zone. Reverse zones aren't tied to domains, nor >vice versa.
>
>>
>>Here's the delegation of your reverse zone, starting from the root
>servers:
>>
>>from f.root-servers.net:
>> 202.in-addr.arpa. NS svc00.apnic.net.
>> 202.in-addr.arpa. NS ns.apnic.net.
>> 202.in-addr.arpa. NS ns.telstra.net.
>> 202.in-addr.arpa. NS ns.ripe.net.
>>
>>from ns.apnic.net:
>> 85.139.202.in-addr.arpa. NS dns1.optus.net.au.
>> 85.139.202.in-addr.arpa. NS dns0.optus.net.au.
>>
>>from dns0.optus.net.au:
>> The host or domain "86.85.139.202.in-addr.arpa." does not exist
>
>>
>>So the class C subnet is delegated to optus.net.au, not to your
>servers. You'll need to discuss this with your provider to resolve it.
>
>I was wondering if you could show me how you generated this info. I
>tried to do this for "my" network (208.247.201.0) using nslookup but
>failed.
Theoretically, you can do this with nslookup, too, but I've never
spent the time to figure out how to send iterative queries (as
opposed to recursive queries) to the servers involved.
I got the above info using DNS Expert's DNS Query tool, which is very
similar in functionality to dig - another tool where I haven't
figured out how to tell it which type of query you want, but at least
it seems to default to iterative queries.
Here's a similar report for your subnet:
from f.root-servers.net:
247.208.in-addr.arpa. NS auth03.ns.uu.net.
247.208.in-addr.arpa. NS auth00.ns.uu.net.
from auth00.ns.uu.net:
201.247.208.in-addr.arpa. NS ns.meridianmap.com.
201.247.208.in-addr.arpa. NS auth00.ns.uu.net.
Note that the reply from auth00.ns.uu.net was marked as
non-authoritative. This indicates that, though it had delegation
records from the class B zone for the class C zone, and though the
class C zone is delegated to itself, it doesn't have a copy of the
class C zone.
So the reverse zone is properly delegated to your server. I noticed
that your server isn't configured for the reverse zone, though. You
should create a reverse zone, then notify your provider that
auth00.ns.uu.net should be configured to act as a secondary server
for the zone.
____________________________________________________________________
Chris Buxton cbuxton@menandmice.com
Men & Mice http://www.menandmice.com
Makers of: QuickDNS Pro
Messages In This Thread:
Return to Digital Point Solutions' Home Page