|
From: Jamie C. <jca...@we...> - 2006-03-07 07:25:53
|
On Tue, 2006-03-07 at 08:02, Robert Moskowitz wrote: > I have just used Webmin to add some subzones for testing purposes and > I discovered some behaviour that I found 'interesting'. > > First, I am running Bind 9.2.4 on Centos 4.2. It is running Chrooted. > > I am logged into Webmin as root > > If I select 'edit Config file', it brings up /etc/named.conf instead > of /var/named/chroot/etc/named.conf Thanks for pointing this out .. that is really a bug, as 'Edit Config File' page is not respecting your chroot settings. > When I created a new master zone, it put the zone file in > /var/named/chroot/var/named (gee, I thought it was suppose to go into > /var/named/chroot/etc? Of course I may have this one wrong). But in > named.conf (and it did edit the one in /var/named/chroot/etc it > specified the file location as: /var/named/zone.file, not > /var/named/chroot/var/named/... That is correct - all the paths in named.conf are relative to the chroot directory. > Next I have put all of my zone file definitions in named.custom and > have a include "/etc/named.custom" in named.conf (which is really in > /var/named/chroot/etc/). I would really like to have all these added > zones also go into named.custom. To do this, click on the Module Config link and set the 'Add new zones to file' option to /etc/named.custom - Jamie |