nslookup error messages.

Brad Knowles brad.knowles at skynet.be
Sun May 20 13:30:44 UTC 2001


At 5:50 PM +0000 5/19/01, Jack Pan wrote:

>            I got a error message when I run the commmand "nslookup"
>
>                  can't find server name for address 192.168.2.10. :
>  non-existent host/domain
>
>  if  anybody knows why,  please give me an advice kindly. I will be
>  greatly appreiciated.

	The problem is that nslookup always does a reverse lookup of the 
nameserver(s) listed in /etc/resolv.conf, and if they are on private 
RFC 1918 IP addresses, those will never succeed.

	The solution is to not use nslookup, but use a proper DNS 
debugging tool such as "dig" (which is part of the BIND package that 
you should have gotten with your system, or that you should have 
installed).

-- 
Brad Knowles, <brad.knowles at skynet.be>

/*        efdtt.c  Author:  Charles M. Hannum <root at ihack.net>          */
/*       Represented as 1045 digit prime number by Phil Carmody         */
/*     Prime as DNS cname chain by Roy Arends and Walter Belgers        */
/*                                                                      */
/*     Usage is:  cat title-key scrambled.vob | efdtt >clear.vob        */
/*   where title-key = "153 2 8 105 225" or other similar 5-byte key    */

dig decss.friet.org|perl -ne'if(/^x/){s/[x.]//g;print pack(H124,$_)}'


More information about the bind-users mailing list