nslookup
Edward Buck
ed at bashware_REMOVEME_.net
Fri Dec 17 23:11:13 UTC 2004
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dean Brooks wrote:
| The issue isn't that dig was poorly written or violates some official
| standard. I was just making a point that a lot of people resist using
| dig because of its arcane and confusing options lists.
I agree that many people resist using dig but it's not because of its
options processing, which makes sense to me. It's because of its overly
verbose default output. Verbosity is a very useful unix convention that
allows various levels of detail. The default for dig includes way too
much information (IMO).
A 'nslookup' on a hostname typically means "get me the A record for that
hostname." A dig on a hostname typically means "get me the A, the NS,
the TTL, the flags and bunch of other detail on a domain name."
I use both nslookup and dig. For simple queries, the output of nslookup
is just easier to read. For troubleshooting, dig is definitely superior.
If dig had a non-verbose option, I would throw away nslookup completely.
~ As it is, I'm quite happy to keep using 'nslookup -sil'.
Cheers,
Ed
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFBw2eP+8K5zYeYuXsRAoI5AJ4v88GFZ2inwWrNH7oliFWKoiW9VQCgykQA
ydQ3zOtLecbYxK9fPZ60QHc=
=on31
-----END PGP SIGNATURE-----
More information about the bind-users
mailing list