Caching-only server problem

Edvard Tuinder listbind at lunytune.nl
Thu Sep 25 09:29:23 UTC 2003


According to Mishari Al-Faris:
> The problem I'm having is, as simple as the configuration of the 
> Caching-only server is, I keep getting the following when I use nslookup 
> on FreeBSD or Linux:
> bash-2.05a# nslookup cnn.com vera2
> *** Can't find server name for address 213.189.95.29: Non-existent 
> host/domain
> *** Default servers are not available

When nslookup starts, it tries to resolve the IP address for the nameserver
to its name. This message tells you that there is no reverse ptr for 213.189.95.29
If it's a very old nslookup it might even perform an IQUERY which is no
longer supported.

If you fix the reverse pointer, nslookup will start working.

> Should I worry about this weird nslookup behavior?

No, nslookup is not the best tool for debugging dns problems. As you showed,
the system performs correct dns lookups when queried with dig. So it works
as it should.

You should however considering setting up a reverse pointer for that IP address.

-Ed


More information about the bind-users mailing list