From owner-freebsd-questions@FreeBSD.ORG Tue May 11 12:31:51 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4469316A4CE for ; Tue, 11 May 2004 12:31:51 -0700 (PDT) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id C68E343D2F for ; Tue, 11 May 2004 12:31:50 -0700 (PDT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin08-en2 [10.13.10.153]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id i4BJVoIE001980; Tue, 11 May 2004 12:31:50 -0700 (PDT) Received: from [10.1.1.193] (nfw2.codefab.com [199.103.21.225] (may be forged)) (authenticated bits=0)i4BJVng4008273; Tue, 11 May 2004 12:31:49 -0700 (PDT) In-Reply-To: <6A7539CE32D1CC42AD0B863337EEFCFB020B20DE@isq004> References: <6A7539CE32D1CC42AD0B863337EEFCFB020B20DE@isq004> Mime-Version: 1.0 (Apple Message framework v613) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: Content-Transfer-Encoding: quoted-printable From: Charles Swiger Date: Tue, 11 May 2004 15:31:47 -0400 To: =?ISO-8859-1?Q?Nuno_C=E9sar_Pires?= X-Mailer: Apple Mail (2.613) cc: "'freebsd-questions@freebsd.org'" Subject: Re: Start BIND on boot X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 May 2004 19:31:51 -0000 On May 11, 2004, at 1:13 PM, Nuno C=E9sar Pires wrote: [ ... ] > The result is that the boot process takes a very long time in the=20 > "Starting > Standard Daemons" [ph]ase. After boot the result of "ndc status" is:=20= > (server is > initialising itself) and then nothing happen. > > Starting de named manually works just fine. Hmm. There isn't enough information available to say what's going on=20 for certain, but what you are doing ought to work fine. Do you have a permanent network connection which is available when your=20= system boots? If the network isn't available, named can't talk to=20 other nameservers and it will probably cause a very long delay which=20 matches your description. Check /var/log/messages after a system reboot for messages relating to=20= named. You ought to see something like this: May 11 15:21:19 pi named[9319]: starting=20 (/etc/named.conf). nam ed 8.3.7-REL Tue Dec 2 14:40:53 EST 2003 =20 root@ns1.pkix.net:/usr/obj/usr/s rc/usr.sbin/named May 11 15:21:19 pi named[9319]: limit files set to=20 fdlimit (1024) May 11 15:21:19 pi named[9320]: Ready to answer queries. May 11 15:21:19 pi named[9320]: check_hints: A records=20 for B.ROOT- SERVERS.NET class 1 do not match hint records If there were problems with your named.conf file or one of the zone=20 files, you'd see warning messages which ought to be fixed. --=20 -Chuck