nslookup tries only first dns in resolv.conf

Barry Margolin barmar at alum.mit.edu
Tue Oct 24 01:08:33 UTC 2006

In article <ehj6sg$2g7a$1 at sf1.isc.org>,
 linuxnewbie1234 <linuxnewbie1234 at nowhere.com> wrote:

> Hi all, not sure it's the right NG but...
> We have an internal network of linux computers, with an internal DNS to 
> resolve internal names, then we have two external DNSs to resolve 
> external names.
> So in the internal computers, resolv.conf contains 3 entries.
> Now, internal linux machines query only the FIRST dns server written in 
> resolv.conf, failing to resolve SOME(*) external names.
> Question: why don't these machines try the other DNSs in resolv.conf? 
> And: what is the proper configuration to make the thing work?

The only time it tries other machines is when the first machine doesn't 
respond.  The intent is to provide failover when the server is down.

If the first server responds, the client believes whatever it says.  If 
it says that a name doesn't exist, they won't ask the second server.

Barry Margolin, barmar at alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***

More information about the bind-users mailing list