Strange nslookup/dns behavior

[Barry Margolin]

In article <9scfr5$nof at pub3.rc.vix.com>,
George Robinson II  <george2 at netchemistry.com> wrote:
>% nslookup ns1.mydomain.com ns1.mydomain.com
>
>	... it comes back nice and happy, but with my secondary, I get...
>-----
>% nslookup ns2.mydomain.com ns2.mydomain.com
>*** Can't find server name for address 192.168.72.123: No response from server
>*** Default servers are not available
>-----
>	However, if I were to run nslookup in interactive mode, it's quite happy and
>have any complaints...

nslookup only requires the server to be able to reverse-resolve its own
address when the server is specified on the command line or gotten from
resolv.conf.  When you use the "server" command it doesn't demand a reverse
lookup.

I don't know why it's schizophrenic about this; I just chalk it up as
another piece of nslookup brain-damage.  Why do you care about such a
broken tool, when there are far superior tools like dig?

-- 
Barry Margolin, barmar at genuity.net
Genuity, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.