Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 06 Sep 2016 10:03:51 +0100
From:      Karl Pielorz <kpielorz_lst@tdx.co.uk>
To:        freebsd-questions@freebsd.org
Subject:   Query re. /etc/resolv.conf...
Message-ID:  <6666070D3E503A5E5747ED16@[10.12.30.106]>

Next in thread | Raw E-Mail | Index | Archive | Help

Hi,

We have a number of 10.3-RELEASE-p7 boxes - on which we use unbound as a 
local DNS / forwarder. Unbound forwards to a pool of 3 DNS servers (this is 
good, because if one fails - unbound handles it).

In '/etc/resolv.conf' we have:

search [blah]
nameserver 127.0.0.1
nameserver 192.168.0.1


We've done this - so that if unbound crashes, the machine should still be 
able to resolve names - it'll just be subject to a delay as the resolver 
library tries 127.0.0.1 (unbound), doesn't get an answer so tries the 
192.168.0.1 name server (kind of as a last resort).


This seems to work OK. However - if we 'turn off' 192.168.0.1, all local 
name resolution is subject to a delay, even if unbound is alive and well - 
and able to forward/resolve names.

Commenting out the 192.168.0.1 nameserver line, and everything works as 
before, but with it listed (and down) the delay comes back.


Can someone confirm this should work that way? - I thought by default it 
was always "try the first, timeout, try the second..."

It doesn't appear to be working that way for us :(

-Kp



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?6666070D3E503A5E5747ED16>