startup, boot vs manually

[Benarson Behajaina]

Bill Larson wrote:
> 
> Another possibility, maybe when starting named at boot time your
> networking is not totally configured and you can't reach any of the
> root name servers.

You are right, there are problems about networking during the
boot time.

So thanks, for your help, I'll check out the firewall,
routing etc during the boot time.

> 
> What info does your log file give you?

from my /var/log/messages

Apr 11 21:03:33 ns1 /usr/sbin/named[542]: starting BIND 9.1.0
Apr 11 21:03:33 ns1 /usr/sbin/named[542]: using 1 CPU
Apr 11 21:03:33 ns1 /usr/sbin/named[544]: loading configuration from '/usr/etc/named.conf'
Apr 11 21:03:33 ns1 /usr/sbin/named[544]: the default for the 'auth-nxdomain' option is now 'no'

it seems that evrything is OK.

I'll try to make my network connectivity allright.

thanks,

Benarson Behajaina
> 
> Bill Larson
> 
> > >>>>> "Benarson" == Benarson Behajaina <Benarson.Behajaina at swh.sk> writes:
> > 
> >     Benarson> - When named is starded at boot time, my name server
> >     Benarson> could not determine IP addresses of hosts which are not
> >     Benarson> in my zone i.e. hosts not in /etc/domain/company.xy
> > 
> >     Benarson> - When I restart the named (manually) with the following
> >     Benarson> command: /etc/rc.d/named stop /etc/rc.d/named start
> >     Benarson> everything works fine.
> > 
> >     Benarson> So, what's is the difference between starting BIND at
> >     Benarson> boot time and manually ?
> > 
> > Maybe you have two different versions of named installed on the
> > computer and perhaps they look at different config files? When you
> > start by hand, the search path is set up so the right version of named
> > runs. At boot time, another one is used. Or the same one with a
> > different config file as an argument.
>