Proper response of reverse lookup private IPs
kcd at daimlerchrysler.com
Fri Mar 16 23:46:05 UTC 2001
The delegated nameservers for 10.in-addr.arpa on the Internet are both called
"blackhole": can you guess why?
If you want 10.*.*.* reverse-lookups to work sanely for your clients, set up
a 10.in-addr.arpa master zone on your nameserver.
Adam Lang wrote:
> My main DNS is hosted by my provider, PSINet.
> I have a BIND server setup for strictly caching (10.10.10.6).
> Currently private IPs are not listed in the DNS.
> I typed in this command at a computer that is using 10.10.10.6 for its DNS
> dig 22.214.171.124.in-addr.arpa PTR
> I get the response (after some time goes by) of
> ; <<>> DiG 8.2 <<>> 126.96.36.199.in-addr.arpa PTR
> ;; res options: init recurs defnam dnsrch
> ;; res_nsend to server default -- 10.10.10.6: Connection timed out
> Is that normal and if so, should it be quicker than 15+ seconds?
> Adam Lang
> Systems Engineer
> Rutgers Casualty Insurance Company
More information about the bind-users