Hmm. First, make sure that it isn't running (service local_unbound stop, etc). Then look at your /etc/resolv.conf -- unbound tends to rewrite that on initial startup, taking some of it's settings and inserting itself into the middle as a caching DNS server. At the very least, you want something like this:nameserver 8.8.8.8 I think the default DHCP client stomps all over /etc/resolv.conf fairly well,
Thats my problem - it doesnt rewrite it :-( I ended up taking one of my machines with a working unboudn setup, rysncing the files to the non working ones, re-enabling unbound and lettign it get on with its life. Have given up on removing it!
Thanks for the advice though, I will dig into it on more detail when I have a moment.
cheers, -pete. _______________________________________________ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
