From owner-freebsd-questions@FreeBSD.ORG Tue Dec 8 20:24:35 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 75F8C106568B for ; Tue, 8 Dec 2009 20:24:35 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 2FED98FC16 for ; Tue, 8 Dec 2009 20:24:34 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.3/8.14.3) with ESMTP id nB8KOY2t042048; Tue, 8 Dec 2009 13:24:34 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.3/8.14.3/Submit) with ESMTP id nB8KOYwV042045; Tue, 8 Dec 2009 13:24:34 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Tue, 8 Dec 2009 13:24:34 -0700 (MST) From: Warren Block To: Derrick Ryalls In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 (wonkity.com [127.0.0.1]); Tue, 08 Dec 2009 13:24:34 -0700 (MST) Cc: FreeBSD Questions Subject: Re: named needs restart after a reboot X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Dec 2009 20:24:35 -0000 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