Date: Tue, 12 Nov 2013 17:53:40 -0500 From: "Gerard Seibert" <jerry@seibercom.net> To: <freebsd-questions@freebsd.org> Subject: RE: unbound and ntp in FreeBSD 10 Beta 3 Message-ID: <005401cedffa$087868d0$19693a70$@seibercom.net> In-Reply-To: <44d2m5b9zc.fsf@be-well.ilk.org> References: <00dc01cedf99$5e1c0cd0$1a542670$@seibercom.net> <44d2m5b9zc.fsf@be-well.ilk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: Lowell Gilbert [mailto:freebsd-questions-local@be-well.ilk.org] > Sent: Tuesday, November 12, 2013 4:12 PM > To: Gerard Seibert > Cc: freebsd-questions@freebsd.org > Subject: Re: unbound and ntp in FreeBSD 10 Beta 3 >=20 > "Gerard Seibert" <jerry@seibercom.net> writes: >=20 > > I just did a fresh install of FreeBSD 10 Beta 3 on a clean machine. > > For whatever reason, I am having the following problem. > > > > I added this to the rc.conf file: > > > > local_unbound_enable=3D"YES" > > > > I also have: > > > > ntpd_enable=3D"YES" > > > > in the file. > > > > This is the resolv.conf file: > > > > #Generated by resolvconf > > #nameserver 209.18.47.61 > > #nameserver 209.18.47.62 > > #nameserver 192.168.1.1 > > > > nameserver 127.0.0.1 > > options edns0 > > > > Now, with this configuration, ntpd never resolves any of the = addresses > > it needs to work. My screen fills up with error messages. If I >=20 > Can any other programs resolve addresses? >=20 > > 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. >=20 > 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. >=20 > If I'm guessing correctly, unbound is not starting at all. You can = test this easily > by enabling unbound and then restarting it. You may get some = informative > information printed out or entered into logs at that time. My guess is = that it > won't actually start at all, and the diagnostic messages will tell you = why. It will > almost certainly be because you didn't set up unbound.conf properly; = very > likely you missed either an "interface" or "forward-zone" setting. >=20 > Good luck. >From what I can find, I only have to place that declaration in the = rc.conf file to get unbound working. I found the info here: = http://blog.des.no/2013/09/local-caching-resolver-in-freebsd-10/ = However, I am not sure if I am also supposed to put the "service = local_unbound start" line into the rc.conf file also. If not; how am I = supposed to start the service? I think the directions could use a = little clarification. --=20 Jerry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?005401cedffa$087868d0$19693a70$>