Date: Wed, 13 Nov 2013 09:14:57 -0500 From: "Gerard Seibert" <jerry@seibercom.net> To: <freebsd-questions@freebsd.org> Subject: RE: unbound and ntp in FreeBSD 10 Beta 3 Message-ID: <002901cee07a$bbafb6d0$330f2470$@seibercom.net> In-Reply-To: <20131113131641.5140ef09@gumby.homeunix.com> References: <00dc01cedf99$5e1c0cd0$1a542670$@seibercom.net> <44d2m5b9zc.fsf@be-well.ilk.org> <20131113131641.5140ef09@gumby.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Tue, 12 Nov 2013 16:12:23 -0500 > Lowell Gilbert wrote: >=20 > > <jerry@seibercom.net> writes: > > > > > uncomment the three nameserver entries it works fine until the = next > > > reboot. I had to comment out the unbound line in the rc.conf file = to > > > prevent it from causing the resolv.conf file from being over = written > > > > > > I obviously have something configured incorrectly. Can anyone help > > > me with this? Also, what do the "options" mean? I cannot find any > > > documentation on it. > > > > There are options documented in resolv.conf(5), but edns0 isn't one = of > > them. I believe it is supported by the libraries on some other > > Unix-ish systems. Most likely, resolv.conf isn't the source of the > > problem, and your version of that file would work fine if unbound = were > > working. > > > > If I'm guessing correctly, unbound is not starting at all. >=20 > This looks like the cause of the problem: >=20 > $ rcorder /etc/rc.d/* | grep -E "ntp|unbound" > /etc/rc.d/ntpdate > /etc/rc.d/ntpd > /etc/rc.d/local_unbound Okay, so was told by someone else on a chat line that the problem was = that "unbound" was not starting first. How should I go about rectifying = that? --=20 Jerry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002901cee07a$bbafb6d0$330f2470$>