The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Fresh install on CentOS - bind failing

Discussion in 'Bind / DNS / Nameserver Issues' started by areh, Jun 2, 2007.

  1. areh

    areh Active Member

    Joined:
    Jul 26, 2002
    Messages:
    44
    Likes Received:
    0
    Trophy Points:
    6
    I'm testing CentOS 5 on a test server at home just to be sure to be able to run a perfect install on the real server if I decide to use it instead of todays RHEL.

    I have done to completely fresh installs: Deleting all partitions. But both times, I do get messages like this in the log. Even if I the second time installed Bind from the packages instead of adding it using Yum.

    "Attempting to locate /etc/named.confno bind configuration present
    Unable to locate Bind configuration file."

    This only appears in the "hidden" install log.

    However, the install finish itself and I thougth that maybe cPanel created an empty named log. However, I do again see the error message above if I try to edit the dns zones.

    So I wonder if there is something I can do during install so that these files is created like cPanel wants them? I can't see that I can do anything different during the install of the OS.

    This migth also be due to me running the system locally, but I want to know why I get this.

    Below is output when I try to activate nameserver after cPanel install.

    Name Server Activated
    Ensuring caching-nameserver is installed
    Loading "installonlyn" plugin
    Setting up Install Process
    Setting up repositories
    Reading repository metadata in from local files
    Excluding Packages in global exclude list
    Finished
    Parsing package install arguments
    Nothing to do
    Activating name server monitoring (chkservd)
    Setting up rndc configuration
    Installing default Bind configuration
    named/
    named/named.zero
    named/localdomain.zone
    named/named.broadcast
    named/named.ip6.local
    named/named.local
    named/localhost.zone
    rndc.conf not located on systemSetting up chroot environment in /var/named/chroot
    rndc.conf not located on systemChecking in /etc/named.conf to rcs system
    Need to create rndc.conf
    Creating rndc.conf
    Copying /etc/rndc.conf to /var/named/chroot/etc/rndc.conf
    Copied /etc/rndc.conf to chroot environment.
    Creating /etc/rndc.key ...
    Copying /etc/rndc.key to /var/named/chroot/etc/rndc.key
    /etc/rndc.key already exists in chroot environment.
    Adding controls clause ...
    Copying /var/named/named.ca to /var/named/chroot/var/named/named.ca
    Copied /var/named/named.ca to chroot environment.
    Copying /var/named/named.ca to /var/named/chroot/var/named/named.ca
    /var/named/named.ca already exists in chroot environment.
    Copying /var/named/named.ca to /var/named/chroot/var/named/named.ca
    /var/named/named.ca already exists in chroot environment.
    Updated /etc/named.conf in chroot directory
    Restarting Bind
    Starting named:
    Error in named configuration:
    /etc/named.conf:65: open: /var/named/named.rfc1912.zones: file not found
    [FAILED]
    Restarting Nameserver
    Starting named:
    Error in named configuration:
    /etc/named.conf:65: open: /var/named/named.rfc1912.zones: file not found
    [FAILED]
    Restarting chkservd
    Stopping chkservd: [ OK ]
    Starting chkservd: [ OK ]
     
  2. dave9000

    dave9000 Well-Known Member

    Joined:
    Apr 7, 2003
    Messages:
    891
    Likes Received:
    1
    Trophy Points:
    16
    Location:
    arkansas
    cPanel Access Level:
    Root Administrator
  3. areh

    areh Active Member

    Joined:
    Jul 26, 2002
    Messages:
    44
    Likes Received:
    0
    Trophy Points:
    6
    I'm not to eager to correct the error just for this box and have to fix this over and over again for each new cPanel install. I would hope for a fix in the distribution if this is an error on all CentOS 5 installations and just not a one time experience (my two new installs should indicate that it is pretty stable (easy reproduceable) error at least on this machine).
     
  4. dave9000

    dave9000 Well-Known Member

    Joined:
    Apr 7, 2003
    Messages:
    891
    Likes Received:
    1
    Trophy Points:
    16
    Location:
    arkansas
    cPanel Access Level:
    Root Administrator
    If you think its a actual problem related to the CentOS5 install then you need to submit a support ticket to cpanel. The forums here are not an official way to contact the support team at cpanel.
     
  5. kyle_h

    kyle_h Member

    Joined:
    Jan 13, 2006
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    0
    CentOS 3.X and 4.X are still the only CentOS versions listed as supported.

    The reason you're having trouble is because CentOS 5 uses bind-9.3 and CentOS 4 uses bind-9.2 - The changes between these versions is significant enough that cPanel won't work with it properly. For instance by default there is no /etc/named.conf file created when bind-9.3 is installed and the default named.conf file for bind-9.3 is significantly different than in older versions.

    Until the code is updated to work with bind-9.3, I have found the workaround to be to remove bind-9.3 packages and install bind-9.2 packages as follows:


    Code:
    yum remove bind-*
    rpm -Uvh --nodeps http://mirror.centos.org/centos-4/4.5/os/i386/CentOS/RPMS/bind-libs-9.2.4-24.EL4.i386.rpm
    rpm -Uvh --nodeps http://mirror.centos.org/centos-4/4.5/os/i386/CentOS/RPMS/bind-utils-9.2.4-24.EL4.i386.rpm
    rpm -Uvh --nodeps http://mirror.centos.org/centos-4/4.5/os/i386/CentOS/RPMS/bind-9.2.4-24.EL4.i386.rpm
    rpm -Uvh --nodeps http://mirror.centos.org/centos-4/4.5/os/i386/CentOS/RPMS/caching-nameserver-7.3-3.noarch.rpm
    ln -s ../../lib/libcrypto.so.0.9.8b /usr/lib/libcrypto.so.4
    service named start
    The --nodeps flag is tagged on because of dependency "libcrypto.so.4" for the bind packages. IMPORTANT! You'll also need to edit /etc/yum.conf and add a line in the [main] section that starts "exclude=" or append to this line if it already exists "bind* caching-nameserver". This prevents yum from updating bind-9.2 to bind-9.3 and in the process breaking cPanel. If you fail to do this when cPanel update is run bind will get updated and the DNS functionality of cPanel will break. I hope this helps shed some light on the issue.
     
    #5 kyle_h, Jun 3, 2007
    Last edited: Jun 3, 2007
  6. airnix

    airnix Registered

    Joined:
    May 17, 2007
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    1
    BIND 9.3.3rc2 on Red Hat Enterprise Linux 5

    Hi,

    Red Hat Enterprise Linux 5 also comes with BIND 9.3.3rc2 so I get the same problem stated above when trying to access A entries and the likes:


    "Attempting to locate /etc/named.confno bind configuration present"

    "Unable to locate Bind configuration file."

    I assume the proposed BIND downgrade would do the trick.

    Anyone could point out how best do the downgrade on RHEL5 ?

    I'm a little lost here.

    Thanx
     
Loading...

Share This Page