Reverse Lookup Bind 9

[James Raftery]

On Wed, Jan 10, 2001 at 09:22:09AM -0500, Ruben I Safir - Brooklyn Linux Solutions CEO wrote:
> One is that NSLOOKUP is not seeing the named server on it's own box.
> *** Can't find server name for address 216.112.229.114: Non-existent
> host/domain
> Server:  hudson.concentric.net
> Address:  207.155.183.72

nslookup is braindead. Seriously, it's hopeless. The problem is that
nslookup can't find a reverse entry for 216.112.229.114. Why it thinks
that's important is anybody's guess. You can shut it up by adding a PTR
for 216.112.229.114 if it's not there already.
OTOH, you should consider using a different tool. Dig is a much better
choice.

> And logs on other machines have problems with reverse DNS of the 192.168
> subnet.  That would make it seem that the darn named is not being seen!!
> 
> /etc/resolv.conf has the rignt nameserver
> domain rm-cpa.com
> search rm-cpa.com

IIRC 'domain' and 'search' are mutually exclusive. Use one or the other.

> *** hudson.concentric.net can't find 192.168.0.106: Non-existent host/domain

hudson doesn't seem to think it's hosting 168.192.in-addr.arpa. Is there
a zone {} clause in the named.conf telling it to load
168.192.in-addr.arpa? At the moment it thinks blackhole.isi.edu it the
master nameserver.

james
-- 
James Raftery (JBR54)
  "Managing 4000 customer domains with BIND has been a lot like
   herding cats." - Mike Batchelor, on dns at list.cr.yp.to.