2 copies of zonefiles

[WebIdentity]

Why has cpanel resorted to using this directory for its zone filing??

/var/named/chroot/var/named/

This is caused so much confusion and just want to know why only after i change entries there things start to work?

[cpanelkenneth]

Why has cpanel resorted to using this directory for its zone filing??

/var/named/chroot/var/named/

This is caused so much confusion and just want to know why only after i change entries there things start to work?

Someone, or something, changed the ROOTDIR value in /etc/sysconfig/named. Do you happen to have the bind chroot RPM installed?

[WebIdentity]

named 24413 0.2 0.3 34740 4796 ? Ssl Oct19 0:14 /usr/sbin/named -u named -t /var/named/chroot

Yeah it looks like its in the sysconfig but no chroot

root@srv03 [~]# yum list bind-chroot
Error: No matching Packages to list
root@srv03 [~]#

[cPanelDon]

Yum is likely not listing it because "bind-chroot" may be in its list of excluded packages.

One easy way to resolve this is to temporarily install the bind-chroot RPM, then immediately remove it, both using yum, but to do this you would need to save a fresh backup of the "yum.conf" configuration file (as detailed below), temporarily edit the bind-chroot entry in the exclude list, then use yum to install and remove the package, followed by restoring the configuration from the backup created.

Here is a basic corrective procedure you could use (if your system uses yum).

1.) Backup:

# cp -pv /etc/yum.conf /etc/yum.conf.backup

2.) Using your preferred command-line text editor via SSH, look for the line beginning with "exclude=" and revise "bind-chroot" to "bind-chroot-temp" where it has a few extra unique characters so it does not match the RPM we need to temporarily use.

/etc/yum.conf

3.) Install "bind-chroot" via yum, then remove via yum:

# yum install bind-chroot
# yum remove bind-chroot

4.) Restore yum configuration from the backup saved in step 1:

# cp -pv /etc/yum.conf.backup /etc/yum.conf

As a final precautionary step, you may want to check to verify named is started, and that chkconfig has named (BIND) configured to automatically start at boot.

Verify status via init script:

# /etc/init.d/named status

If needed, start or restart:

# /etc/init.d/named restart

Verify "chkconfig" setting:

# chkconfig --list named

If needed, correct "chkconfig" setting:

# chkconfig --level 35 named on