Date: Tue, 8 Dec 2009 13:24:34 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: Derrick Ryalls <ryallsd@gmail.com> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: named needs restart after a reboot Message-ID: <alpine.BSF.2.00.0912081320350.41895@wonkity.com> In-Reply-To: <d5eb95fc0912081117s31fda52am2e73434189802072@mail.gmail.com> References: <d5eb95fc0912081117s31fda52am2e73434189802072@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 8 Dec 2009, Derrick Ryalls wrote: > uname: > > FreeBSD example.com 8.0-RELEASE-p1 FreeBSD 8.0-RELEASE-p1 #0: Sun Dec > 6 11:23:52 PST 2009 ryallsd@example.com:/usr/obj/usr/src/sys/FRODO > amd64 > > I have most things working, but I have noticed that every time I > reboot the machine, I need to manually restart named to get it > listening on the proper interfaces as by default it is listening on > 127.0.0.1 interfaces only. A simple /etc/rc.d/named restart fixes it > which seems like it would be configured correctly, but I have had to > do this on a install before. > > Anyone have a guess as to what could be wrong? Only a guess: network interface comes up too late. If you're using DHCP to configure that interface, you could try SYNCDHCP. Or if it's an re(4) interface, there are patches in 8-STABLE that make it come up faster. -Warren Block * Rapid City, South Dakota USA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0912081320350.41895>