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.
Log in to post a comment.