Start BIND on boot

[Charles Swiger]

On May 11, 2004, at 1:13 PM, Nuno César Pires wrote:
[ ... ]
>  The result is that the boot process takes a very long time in the 
> "Starting
> Standard Daemons" [ph]ase. After boot the result of "ndc status" is: 
> (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 
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 
other nameservers and it will probably cause a very long delay which 
matches your description.

Check /var/log/messages after a system reboot for messages relating to 
named.  You ought to see something like this:

May 11 15:21:19 <daemon.notice> pi named[9319]: starting 
(/etc/named.conf).  nam
ed 8.3.7-REL Tue Dec  2 14:40:53 EST 2003       
root at 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 
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 
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 
files, you'd see warning messages which ought to be fixed.

-- 
-Chuck