Re: [webmin-l] Bind Oddities

[Jamie C. <jca...@we...>]

On 01/Dec/2012 20:01 John Hinton <web...@ew...> wrote ..
> On 12/1/2012 8:19 PM, Jamie Cameron wrote:
> > On 30/Nov/2012 19:00 John Hinton <web...@ew...> wrote ..
> >> I am running CentOS 6 with bind in a chroot environment. Have the same
> >> setup on some C5 servers. It worked great until a few weeks ago.
> >> Suddenly the Webmin system seemed to lose the pathing info. So, I have
> >> messed around with pretty much everything and here is where I am.
> >>
> >> Bind runs fine from the command line.
> >> There were no updates to bind when this happened.
> >> Named is seen as running in bootup and shutdown module.
> >> Named is not seen as running nor will it start via the Webmin interface.
> >> All of the existing zone files are empty in the Webmin module, however
> >> they are not empty on the server.
> >> I created a dummy domain entry and it used the full path to the zone
> >> files instead of using my selection to use relative zone file paths.
> >> And, I can see inside the files in the bind module and can see records
> >> created from the command line.
> >>
> >> So, this seems like somehow bind has lost it's wits about the chroot
> >> pathing. I checked sysconfig/name and ROOTPATH is correct. If I set it
> >> to use my /var/named/chroot directory set in webmin instead of running
> >> the shell script, I get the same results.
> >>
> >> I have run round and round in circles on this. Any ideas on where to look?
> > In Webmin's BIND module, does it show at the top of the main page that BIND
> > is under a chroot directory?
> I have three nameservers. On this one it does not. FYI, it worked right 
> for months and then suddenly stopped. I never allow any bind updates 
> except on my command as Redhat seems to break the permissions on slaves 
> during each upgrade.
> 
> I have set every setting that I can think of differently. It finds 
> named.conf correctly, but is confused about the location of the zone 
> files. if I create a new one, it is placed where ever the path to the 
> zone files is set and the chroot is not considered. If I set the path to 
> the full chroot directory, it places the zone file there and it is seen 
> and editable, but the path in named.conf is also the full path including 
> the chroot directory.

Are all three nameservers running CentOS 6? Version 6 introduced some changes
in the way the BIND chroot is setup that has caused problems for some Webmin users.

Personally I would recommend not running in chroot if you can. The security
benefits are minimal..

 - Jamie