|
|
 |  |
reverse lookupsFrom: Scott Tudor Date: Tuesday, April 18, 2000
Time: 8:23:58 amI 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.
|

Return to Digital Point Solutions' Home Page |