WebIdentity

Member
Mar 27, 2004
17
0
151
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

cPanel Development
Staff member
Apr 7, 2006
4,608
77
308
cPanel Access Level
Root Administrator
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?
 

cPanelDon

cPanel Quality Assurance Analyst
Staff member
Nov 5, 2008
2,545
12
268
Houston, Texas, U.S.A.
cPanel Access Level
DataCenter Provider
Twitter
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:
Code:
# 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.
Code:
/etc/yum.conf
3.) Install "bind-chroot" via yum, then remove via yum:
Code:
# yum install bind-chroot
# yum remove bind-chroot
4.) Restore yum configuration from the backup saved in step 1:
Code:
# 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:
Code:
# /etc/init.d/named status
If needed, start or restart:
Code:
# /etc/init.d/named restart
Verify "chkconfig" setting:
Code:
# chkconfig --list named
If needed, correct "chkconfig" setting:
Code:
# chkconfig --level 35 named on