Date: Wed, 19 May 2004 14:24:02 +0100 From: =?iso-8859-1?Q?Nuno_C=E9sar_Pires?= <NCPires@isq.pt> To: 'Charles Swiger' <cswiger@mac.com>, =?iso-8859-1?Q?Nuno_C=E9sar_Pir?= =?iso-8859-1?Q?es?= <NCPires@isq.pt> Cc: "'freebsd-questions@freebsd.org'" <freebsd-questions@freebsd.org> Subject: RE: Start BIND on boot Message-ID: <6A7539CE32D1CC42AD0B863337EEFCFB020B20F2@isq004>
next in thread | raw e-mail | index | archive | help
Hi, Sorry not to give my feedback related with your suggestions sooner, but = I was absent. I have looked to the named messages after boot and apparently it was everything ok i.e.: First message: "starting (etc/namedb/named.conf). named 8.3.6-REL = ....." Second message: "limit files set to fdlimit (1024)" Third message: "Ready to answer queries." There is no messages related with the ROOT SERVERS, the file was = updated and there is a permanent network connection. Running the "ndc status" the output is: "server is initialising itself" After restarting the server manually, after boot, the status is: = "server is up and running". The result after comment the kern_securelevel=3D"2" and kern_securelevel_enable=3D"YES" lines in the rc.conf and reboot was the = same as described above. Do you have any more suggestions to debug and solve this problem? Thanks Nuno -----Original Message----- From: Charles Swiger [mailto:cswiger@mac.com]=20 Sent: ter=E7a-feira, 11 de Maio de 2004 20:32 To: Nuno C=E9sar Pires Cc: 'freebsd-questions@freebsd.org' Subject: Re: Start BIND on boot 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" phase. 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 = 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 <daemon.notice> 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 <daemon.warn> pi named[9319]: limit files set to=20 fdlimit (1024) May 11 15:21:19 <daemon.notice> pi named[9320]: Ready to answer = queries. May 11 15:21:19 <daemon.warn> 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 =20 CONFIDENCIALIDADE: Esta mensagem e quaisquer documentos em anexo s=E3o confidenciais. Se n=E3o for o destinat=E1rio desta mensagem, = agradecemos que avise imediatamente o remetente e que a elimine sem a reproduzir, = armazenar ou divulgar a qualquer entidade. CONFIDENTIALITY: This e-mail and any attachments are confidential = and may be privileged. If you are not a named recipient, please notify the = sender immediately and do not disclose the contents to another person, use it = for any purpose or store or copy the information in any medium.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6A7539CE32D1CC42AD0B863337EEFCFB020B20F2>