#4177 Bind-Chroot broken on Centos 6.3

1.610
closed-fixed
5
2013-03-05
2012-12-18
Anonymous
No

The bind module does no longer work with a chrooted environment,
regardless the settings in the module configuration and /etc/sysconfig/named,
zones will be displayed but not view- or editable.
Also, the configuration check will fail.

Settings tested in module.config:
- explecitely setting chroot directory
-additionally defining an absolute path for the zone files

This problem is also handled here:
Bind 8 Fails after upgrade to 1.590 - ID: 3545107
In our case, turning of the chroot environment unfortunately isn`t an option.

The Problem seems to exist with every version greater than 1.570-1.

Workaround: Install 1.570-1 Version if you are required to run bind in a chrooted environment und Centos 6.3 or similar.

Discussion

  • Jamie Cameron

    Jamie Cameron - 2012-12-19

    Webmin shouldn't actually need to know about the chroot environment on CentOS 6, as in the default BIND setup all the configuration and zone files have the same paths inside and outside the chroot. This is implemented using loopback mounts.

    Is this the case on your system?

     
  • Comment has been marked as spam. 
    Undo

    You can see all pending comments posted by this user  here

    Anonymous - 2012-12-27

    Hi,
    yes:

    /etc/named on /var/named/chroot/etc/named type none (rw,bind)
    /etc/named.rfc1912.zones on /var/named/chroot/etc/named.rfc1912.zones type none (rw,bind)
    /etc/rndc.key on /var/named/chroot/etc/rndc.key type none (rw,bind)
    /usr/lib64/bind on /var/named/chroot/usr/lib64/bind type none (rw,bind)
    /etc/named.iscdlv.key on /var/named/chroot/etc/named.iscdlv.key type none (rw,bind)
    /etc/named.root.key on /var/named/chroot/etc/named.root.key type none (rw,bind)

     
  • Jamie Cameron

    Jamie Cameron - 2012-12-27

    Which directory actually contains your zone files though?

     
  • Comment has been marked as spam. 
    Undo

    You can see all pending comments posted by this user  here

    Anonymous - 2012-12-28

    Zone files are in /var/named/chroot/var/named/.

    Pathes/files in named.conf:

    options {
    directory "/var/named";
    ...

    zone "foo.dom" {
    type master;
    file "foo.dom.hosts";
    ...

    (I`ve also tried absolute pathes for zones files)

     
  • Jamie Cameron

    Jamie Cameron - 2013-03-05

    Webmin 1.630 will fix this issue, by properly handling CentOS 6.x systems that have a chroot enabled, but aren't using the loopback mounts typically setup by the bind-chroot package.

     
  • Jamie Cameron

    Jamie Cameron - 2013-03-05
    • status: open --> closed-fixed
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks