named.conf cannot be changed

[Kevin Darcy]

Doyle Collings wrote:
> I am running BIND 9.2 on Suse 9.3.  I am trying to add the location of the
> slave file in named.conf using the following syntax: 
> file "slave/loganutah.org";
>
> when I restart my dns server by issuing a named stop and named start
> command, the line is taken away from the zone configuration?  If I move the
> named.conf file and restart the server using the same procedure, the
> named.conf reappears in the var/lib/named/etc/ location.  What process is
> writing the file to the location? Should I be editing named.conf from
> another location?
>   
This is not really a BIND question -- BIND itself only takes named.conf 
as *input*.

There must be something in your OS, or some third-party package, which 
is trying to "manage" your nameserver configuration somehow.

Since your named.conf is getting modified from a simple "named 
stop"/"named start" command sequence, I'd look into what "named" is 
invoking on your system. Maybe it's just some wrapper script that in 
turn invokes this "management" system that's trying to do you some favors...

                                                                         
                     - Kevin