host versus nslookup

Mark Andrews marka at
Thu Oct 13 02:08:52 UTC 2011

In message <040B89C8B1E1D945AE2700C511A039E905A0E5 at>, "Lightne
r, Jeff" writes:
> One thing that is different about nslookup on HP-UX (which doesn't have host)
>  is that it actually respects nsswitch.conf so will give you results from /et
> c/hosts OR from name services whereas most implementations only do it from na
> me services.

It shouldn't.  The NS in nslookup stands for NAMESERVER.  Nslookup
is a diagnostic tool for the DNS and corrupting it to lookin
/etc/hosts, NIS, YP, LDAP is just wrong.

> Nslookup is "deprecated" meaning you should use host where possible.   Also f
> or DNS troubleshooting dig is a much better tool than nslookup or host.
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka at

More information about the bind-users mailing list