Everyone who has responded so far (thanks and you can stop now!) has
pointed out that on solaris, nslookup is strictly a dns tool.
Well, next time I'll read things even more carefully. I was snookered by
the fact that HP's implementation of nslookup has been extended to use
nsswitch. From the HP nslookup manpage:
"nslookup has been extended to follow the configured name resolution
algorithm of the host and to query NIS, as well as, DNS and host
Seems to me that this is pretty useful and sun might consider implementing
Also the sun nslookup man page refers to the resolver docs which clearly
talk about using nsswitch, but I forgot that nslookup doesn't do a
gethostbyname, simply looks things up in the tables.
Just for grins, I checked a linux box and it too doesn't have the nsswitch
extension. Oh well.
/ Sid /
> If a system is NOT in dns, but IS in the hosts file, nslookup fails.
> It appears as though nslookup is not using nsswitch to determine its
> resolver "search order". ping and other network programs will find the
> host, but nslookup will not. (nsswitch has the "hosts: dns files"
> This makes it hard to do some network troubleshooting.
> Am I wrong? Or is there a fix?
> / Sid /
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:14:02 CDT