Re: [webmin-l] Problem with BIND module config

[Robert M. <rg...@ht...>]

On 02/14/2013 08:11 PM, Jamie Cameron wrote:
> On 14/Feb/2013 16:41 Robert Moskowitz <rg...@ht...> wrote ..
>> On 02/14/2013 07:05 PM, Jamie Cameron wrote:
>>> On 14/Feb/2013 14:34 Robert Moskowitz <rg...@ht...> wrote ..
>>>> Again Centos 6.3 and Webmin 1.610
>>>>
>>>> I am running BIND chrooted.  I go into the BIND DNS screens and it is
>>>> showing the files under /etc
>>>>
>>>> My /etc/sysconfig/named properly points the ROOTDIR to /var/named/chroot
>>>> but Webmin is not picking this up.
>>>>
>>>> In the configuration options it is showing NONE for the chroot directory
>>>> to run BIND under.
>>>>
>>>> Changing this option and it still is pointing to the /etc files.
>>>>
>>>> I know that BIND is running chrooted, as /var/log/messages show all the
>>>> zones loading at start.
>>> Normally with CentOS 6, Webmin doesn't need to know about the chroot
>>> directory, because all the files are under /etc or /var/named, and
>>> linked to from within the chroot via loopback mounts. Is that the case on
>>> your system?
>> I put all the files properly into the chroot directories:
>>
>> /var/named/chroot
>>      /etc
>>      /var/named
>>
>> Per the Redhat documentation:
>>
>> https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1-BIND.html
>>
>> They are only there.  I have been doing this ever since I chrooted in
>> Linux.  Definitely the way I have it on my current Centos 5.5 system
>> that Webmin is finding the files (but perhaps I had to change the config
>> there way back when).
>>
>> So, no the files are not in /etc or /var/named and no symlinks to those
>> directories (though the non-chrooted files you get on installing bind
>> itself are there).  You are suppose to follow ROOTDIR= from
>> /etc/sysconfig/named.
> It looks like there is a difference in how BIND is setup chrooted by
> default on CentOS 6, and how you have it.

I did a clean install.  The bind rpm put the named.conf into /etc along 
with a few other files.  The bind-chroot created the /var/named/chroot 
tree but did not put any files there.  Perhaps they changed in 6.3 from 
prior 6 releases?  I am 'use' to finding a number of files in 
/var/named/chroot/etc and editing/replacing/adding, perhaps I should 
download the rpms directly and look into them to see what they really have.

>   However, Webmin should be able to handle that

You should use the ROOTDIR= directive.

>   - does the /etc/named.conf file exist on your system,
> and if so is it a regular file or a symlink to somewhere?

It is there and a regular file.  Put there by the bind rpm and not 
removed by the bind-chroot rpm.

> This information will allow me to modify webmin to handle chroot setups
> like yours.
Glad to help.  I use webmin to more easily edit the zone files, as I 
have been editing zone files since I started doing my own DNS in '95.  
But for DNSSEC, I will probably use more of your functionality.