From: Jamie C. <jca...@we...> - 2006-05-23 07:42:51
|
On 23/May/2006 01:06 Thomas Cameron wrote .. > Jamie Cameron wrote: > > On 22/May/2006 22:35 Thomas Cameron wrote .. > > > >> Howdy All - > >> > >> I did a cursory search and didn't find anyone else who has run into > >> this, forgive me if this has already been discussed. > >> > >> I am running webmin-1.270-1 installed from RPM on a RHEL 4 AS i386 > >> server. The server is up to date as of today. It has > >> caching-nameserver-7.3-3, bind-libs-9.2.4-2, bind-chroot-9.2.4-2, > >> bind-9.2.4-2 and bind-utils-9.2.4-2 installed. When I create DNS zone > >> files, they are created as expected in /var/named/chroot/var/named. > >> However, the /etc/named.conf file is configured by webmin to look for > >> the files under /var/named. The other zones files in > >> /var/named/chroot/var/named are symlinked to /var/named, but webmin > does > >> not create the appropriate symlinks for those files it creates. > >> > >> Is this a webmin bug? > >> > > > > Maybe :) > > Is it really necessary to create synlinks from /var/named to the chroot > > directory? > > Honestly, I would think that sort of negates the whole point of chroot > anyway. Not sure what the logic behind that is. > > > Normally when BIND is run in a chroot environment, it will always > > look for named.conf and the zone files under /var/named/chroot , meaning > that > > the files under /var/named are never accessed directly. > > Makes sense, but in my case it was not working until I created the symlinks. What went wrong exactly? If the zone files were missing from BIND's point of view, you would have gotten errors in /var/log/messages saying so when it was started.. > > So Webmin doesn't > > bother to create then .. > > > > - Jamie > > OK. I will poke around and see if there was something knuckle-headed I > did and just don't realize it. > > Thanks! > TC > > PS - Jamie, are you Clan Cameron of Lochiel? No idea - the Camerons in my family emigrated to australia several generations back.. - Jamie |