|
|
 |  |
Re: reverse lookupsFrom: Global Homes Webmaster Date: Tuesday, April 18, 2000
Time: 10:19:19 amOn 04/18/00 at 11:16, Scott Tudor wrote:
> 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.
>
> Thanks for all great information.
The information above was probably obtained using the excellent DNS Expert
that comes with QDNS. There are a variety of other tools for MacOS, including
AGNetTools and WhatRoute, that can also be used to do DNS queries. The
advantage of DNS Expert is that it can analyze the DNS information it gets
from queries, rather than simply displaying it and leaving analysis up to the
user. You can also get the same info using either nslookup or dig on a *nix
machine. With nslookup, you'd want to use its 'interactive' mode so that you
can use the 'server' command to specify the name server you want to query.
With dig, you can use the @ operator in the command line. Both nslookup and
dig are described in a fair amount of detail in their respective man pages.
Christopher Bort
|

Return to Digital Point Solutions' Home Page |