Query re. /etc/resolv.conf...
emorrasg at yahoo.es
Tue Sep 6 14:44:58 UTC 2016
On Tue, 06 Sep 2016 10:03:51 +0100
Karl Pielorz <kpielorz_lst at tdx.co.uk> wrote:
> 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..."
Are you sure unbound listen on 127.0.0.1? What a
%sockstat | grep unbound
unbound unbound 527 3 udp6 ::1:53 *:*
unbound unbound 527 4 tcp6 ::1:53 *:*
unbound unbound 527 5 udp4 127.0.0.1:53 *:*
unbound unbound 527 6 tcp4 127.0.0.1:53 *:*
unbound unbound 527 7 stream /var/run/local_unbound.ctl
unbound unbound 527 8 stream -> ??
unbound unbound 527 9 stream -> ??
> It doesn't appear to be working that way for us :(
> freebsd-questions at freebsd.org mailing list
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscribe at freebsd.org"
Eduardo Morras <emorrasg at yahoo.es>
More information about the freebsd-questions