bind-users April 2010 archive
Main Archive Page > Month Archives  > bind-users archives
bind-users: Re: Unexpected issues with "nslookup" comm

Re: Unexpected issues with "nslookup" command

From: Barry Margolin <barmar_at_nospam>
Date: Mon Apr 19 2010 - 01:08:07 GMT

In article <>,
 James Roberts-Thomson <> wrote:

> However, I'm not sure why it was working when only one nameserver was
> specified if the server wouldn't allow recursion in the first place. The
> nameservers are supposed to be authoritative for the domains in question in
> the first place, so I'm not sure why recursion was an issue anyway.

Are the servers authoritative for your reverse domain as well? A
misfeature of nslookup is that before it sends to query you asked it
for, it first does a reverse lookup of the server IP, so that it can
report the name of the server it's using.

But if there's only one server, it will apparently use it regardless of
the error.

If you're trying to troubleshoot DNS, you really should use "dig" rather
than "nslookup".

-- Barry Margolin, Arlington, MA *** PLEASE don't copy me on replies, I'll read them in the group *** _______________________________________________ bind-users mailing list