Maybe I should have provided a few more bits of info...
Out of the box full FC3 install has the chrooted files are linked back into the non-chroot location which is /var/named. Webmin will work with it and see it as long as all files are linked back to /var/named. Which is the way it is until you add new zone files then one needs to manually locate them to the chroot location and link the files back out. All works well.
Currently my DNS server is working very well, but I can not control it with the 'service named ....' or Webmin. I can modify it with Webmin, but not stop or start it. It requires a reboot to take up the changes. All files are standard out of the box installation except for my added in zone files. This also was working without this start & stop issue up to yesterday afternoon, but not working well with the other clients on the network. I fixed a couple of things and somewhere along the way it broke. Guess I need to go backwards in the configuration and work my way back out of it to see if it starts working with the tools again. Dig and nslookup both work fine with this too.
I have one suggestion to look at the rndc.key portions of the configuration which I will do this afternoon.
Bill
Craig wrote:
----
No - you are probably suffering through the ravages of different
programs locating different files in different places and the things
that webmin's BIND module does to a file & zonefiles vs what system-
configbind will do to the conf file & zone files are not
interchangeable.
If you look at the file locations specified in /etc/init.d/named, you
will see a reference to {ROOTDIR}
If you look at the file /etc/sysconfig/named you will see comments like:
# Currently, you can use the following options:
# ROOTDIR="/some/where" -- will run named in a chroot environment.
# you must set up the chroot environment
before
# doing this.
# OPTIONS="whatever" -- These additional options will be passed to named
# at startup. Don't add -t here, use ROOTDIR
instead.
Then if you look at 'module config' options in the BIND module in
Webmin, you will see that everybody doesn't agree with where things are
at.
Since you have webmin working, best to adjust /etc/sysconfig/named to
play along. If you have webmin running 'named' chrooted, - i.e.
named.conf is located in /var/named/chroot/etc directory, then the
'ROOTDIR' in /etc/sysconfig/named should be set to /var/named/chroot
The reason the cli commands to service named restart and such work
properly is because it has to locate the main config file, the zone
files (which are referenced in the main named.conf) and the pid files,
all of which are relocated when named is chrooted.
Craig
