Re: named needs restart after a reboot
On Tue, Dec 8, 2009 at 12:24 PM, Warren Block wbl...@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 ryal...@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 ifconfig_nfe0=SYNCDHCP Was the fix, thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: named needs restart after a reboot
On Wed, Dec 9, 2009 at 3:39 PM, Derrick Ryalls ryal...@gmail.com wrote: On Tue, Dec 8, 2009 at 12:24 PM, Warren Block wbl...@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 ryal...@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 ifconfig_nfe0=SYNCDHCP Was the fix, thanks! Spoke too soon. On one reboot, the interface couldn't talk to DHCP until I set it down then back up. I have gone to statically setting the IP. Not ideal, but seems to be working (based on one clean reboot). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
named needs restart after a reboot
Greetings, uname: FreeBSD example.com 8.0-RELEASE-p1 FreeBSD 8.0-RELEASE-p1 #0: Sun Dec 6 11:23:52 PST 2009 ryal...@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? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: named needs restart after a reboot
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 ryal...@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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
