Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 9 Dec 2009 15:39:00 -0800
From:      Derrick Ryalls <ryallsd@gmail.com>
To:        Warren Block <wblock@wonkity.com>
Cc:        FreeBSD Questions <freebsd-questions@freebsd.org>
Subject:   Re: named needs restart after a reboot
Message-ID:  <d5eb95fc0912091539l2469118avb4f223435ff7e985@mail.gmail.com>
In-Reply-To: <alpine.BSF.2.00.0912081320350.41895@wonkity.com>
References:  <d5eb95fc0912081117s31fda52am2e73434189802072@mail.gmail.com> <alpine.BSF.2.00.0912081320350.41895@wonkity.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Tue, Dec 8, 2009 at 12:24 PM, Warren Block <wblock@wonkity.com> wrote:
> 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 =A0 =A0 ryallsd@example.com:/usr/obj/usr/src/sys/FRO=
DO
>> 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. =A0A 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. =A0If you're using DHC=
P to
> configure that interface, you could try SYNCDHCP. =A0Or 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
>

ifconfig_nfe0=3D"SYNCDHCP"

Was the fix, thanks!



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?d5eb95fc0912091539l2469118avb4f223435ff7e985>