resolve.conf

mvrk · 11-13-2013, 06:42 AM

Hi,

I've got this configuration on my resolv.com

search domain1.local domain2.local
nameserver 192.168.1.1
nameserver 192.168.2.1

192.168.1.1 only knows domain1.local
and
192.168.2.1 only knows domain2.local

If both DNS servers are up, i can't resolve names of domain2.local i allways get this:

nslookup app1.domain2.local
Server: 192.168.1.1
Address: 192.168.1.1#53

** server can't find app1.domain2.local: NXDOMAIN

And it never tries second server.

Anyway to make the resolution try next server when name not found?

Zarniwoop79 · 11-13-2013, 08:19 AM

I usually don't have this problem butafter reading the man-page it seems that "ndots" might be the solution. I don't quite follow how to config it, but I found this in the manpage:

From the explanation of "search" on the resolv.conf-manpage:

Code:

Resolver queries having fewer than ndots dots (default is  1)  in  them
              will  be  attempted using each component of the search path in turn until a match is found.

Explanation of ndots in the resolv.conf manpage:

Code:

ndots:n
                     sets  a  threshold  for  the  number  of  dots  which must appear in a name given to res_query(3) (see
                     resolver(3)) before an initial absolute query will be made.  The default for n is 1, meaning  that  if
                     there  are any dots in a name, the name will be tried first as an absolute name before any search list
                     elements are appended to it.  The value for this option is silently capped to 15.

I don't fully follow, but based on this it seems that if you set "ndots" to a high number it should search all (both in your case) the domains before giving up.