Search Again:

Re: bind usage

From: Len Conrad
Date: Saturday, July 19, 2003
Time: 8:22:26 am


>I recently added a new name server, everything seems to work fine via
>quickdns manager, but when I do a lookup to the server I get:
>
>nslookup www.facethejury.com ns2.mydomain.com
>*** Can't find server name for address xxx.xxx.xxx.xxx: Non-existent
>host/domain
>*** Default servers are not available
>
>Whats going on?

nslookup is screwed up, most versions are (but recent versions delivered
with BIND are fixed), in that when told to use ns2.mydomain.com as DNS, it
resolves for the A record xxx.xxx.xxx.xxx of the DNS, and then queries for
its PTR "server name" (who asked for that?). If no PTR, then nslookup fails
("non-existnet host/domain"), causing "false" problems. The failure to
find the nslookup's prerequisite PTR is nslookup's own making, and has
nothing to with your query. A huge software design fault.

use dig

Len




Messages In This Thread:



Return to Digital Point Solutions' Home Page