nslookup and bind 8.2.1

Michael Voight mvoight at cisco.com
Mon Aug 23 16:25:22 UTC 1999


The ability to use nslookup should not be confused with the inability to
resolve. nslookup requires you be able to resolve the addresses of your
servers, the resolver doesn't. Do you have PTR records for the addresses
listed below?

Michael

blip wrote:
> 
> Hello,
> 
> We have recently installed bind 8.2.1 on solaris 2.6.  Install went ok,
> and went to check
> things with nslookup.
> 
> When we run the nslookup command, the following results:
> 
> % nslookup
> *** Can't find server name for address 63.73.223.69: Non-existent
> host/domain
> *** Can't find server name for address 63.73.223.70: Non-existent
> host/domain
> *** Default servers are not available
> 
> We have checked our named.conf file extensively for syntax errors and
> have found
> none.   All zones appear to be loading ok, and very rarely do we get an
> unresolvable
> host name, due to bind 8.2.1.
> 
> Any help much appreciated,
> 
> TIA,
> 
> Morgan


More information about the bind-users mailing list