[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Cannot rename /etc/named.boot to $Named_disabled
- Subject: Re: [cobalt-users] Cannot rename /etc/named.boot to $Named_disabled
- From: "Gerald Waugh" <gerald@xxxxxxxxx>
- Date: Tue Jul 17 00:33:48 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
As indicated below, when i try to stop the server from the
control panel the message changes to "Cannot rename
/etc/named.boot to $Named_disabled" (again it seems from the
file names that it is trying to turn it on when i uncheck
the box???)
I get a funny feeling that the RaQ is somehow confused about
the state of the DNS server. It shows it checked off, and
starts the swatch, even though it's not able to start it.
It's almost like the SQL database is backward with repeat to
the state of the DNS server? But that is just a guess??? I
am very unsure what to do next.
What version of bind are you running?
The /etc/named.boot file is a "bind version 4" configuration
file.
You must be running a RaQ2.
I read somewhere that the RaQ2 GUI uses the /etc/named.boot
file,
Then runs a conversion script (named-bootconf.pl) to convert
named.boot to bind bind 8 /etc/named.conf.
I have a RaQ2, but I don't use the GUI for DNS. So my system
does not use named.boot.
Probably no-help, but some information.
Gerald