Query re. /etc/resolv.conf...
kpielorz_lst at tdx.co.uk
Tue Sep 6 09:04:05 UTC 2016
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:
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 :(
More information about the freebsd-questions