[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: why dig ? I wanna use nslookup !

Gerrit Pape writes:
> On Wed, May 02, 2001 at 01:27:56PM +0200, Paul Slootman wrote:
>> On Tue 01 May 2001, Marco d'Itri wrote:
>>> nslookup is broken, please let it die its long-deserved death.
>> What's broken about it, apart from the brokenness that's in the current
>> version about the verbose warnings and missing features (eg. ls) ?
>> AFAIK it does exactly what it was designed to do. This is like saying
>> "ed is broken, use emacs", while ed performs its task perfectly.
> See http://cr.yp.to/djbdns/faq/tinydns.html#nslookup f.e.

...which says:

| What exactly is nslookup doing wrong? Three things:
|     * Before doing what you tell it to do, nslookup tries a PTR query
|       on the server's IP address, so that it can tell you the server's
|       name, as if this information were more useful than the name or
|       IP address that you gave nslookup in the first place.
|     * When you specify a server on the command line, nslookup sends
|       its silly PTR query to that server, unjustifiably assuming that
|       the server is recursive or already has the answer. Correct
|       behavior would be to ask the local cache.
|     * If the silly PTR query fails, nslookup aborts, and never does
|       what you told it to do.

That looks like a requirement to remove a few lines of code, rather
than to retire the whole program.  So what else is wrong with it?


Reply to: