On Fri, 30 Mar 2001, Steve Keay wrote:
> nslookup does a rather dumb thing:  it tries to lookup the reverse DNS
> for the nameserver it's about to use.  Apart from being a waste of
> time, failure to find the name means it will refuse to query that
> nameserver.

Why doesn't your nameserver *have* reverse DNS.

> nslookup is a throwback to 1970's UNIX bollocks, as is the whole of
> the BIND distribution.  If you have to use anything from BIND, host
> and dig are at least somewhat consistent....

host(1)'s error messages are often misleading - it can give the message
"try again" to nxdomain responses, for example...


Matthew Byng-Maddick   Home: <[EMAIL PROTECTED]>  +44 20  8980 5714  (Home)
http://colondot.net/   Work: <[EMAIL PROTECTED]> +44 7956 613942  (Mobile)
There are worse things in life than death.  Have you ever spent an evening
with an insurance salesman?                                 -- Woody Allen

Reply via email to