The disgusting and useless nslookup

[Brad Knowles]

At 4:37 PM -0400 5/26/01, Chip Old wrote:

>  In the scenario Bob described, he is troubleshooting local resolver
>  issues, not DNS issues.  He needs to be able to see name resolution as the
>  local machine sees it, including whatever effect the local hosts file and
>  NIS may have.  In that scenario nslookup will verify that there is a
>  problem, then dig will tell you if the problem is in DNS.  If dig sees no
>  problem but nslookup does, then chances are good that it's a problem in
>  /etc/hosts or NIS.

	Indeed, that is precisely the situation where nslookup is the 
most useless, precisely because it avoids using the standard resolver 
routines, and doesn't go through /etc/nsswitch.conf, etc....

	If people want to argue this point, they really need to get their 
facts straight as to just exactly what nslookup does and how it does 
it.

-- 
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,$_)}'