Article ID: 2208, created on Sep 27, 2007, last review on Mar 8, 2015

  • Applies to:
  • Odin Business Automation Standard 4.5

Symptoms

I've registered name servers based on RedHat EL 5/CentOS 5/FedoraCore 5 or FedoraCore 6 in Parallels Business Automation - Standard (PBA-S) according to Registering Name Server Managed via SSH.

However, the name server still has an "Error" status.

Cause

BIND misconfiguration on the name server.

Resolution

For new name servers based on RedHat EL 5/CentOS 5/FedoraCore 5/FedoraCore 6 distributions, the following changes should be performed before registration in PBA-S:

  • Install bind if the package is missing on the server

    ~# rpm -q bind
    package bind is not installed
    ~# yum install bind
    ...
    
  • Verify that the file /etc/named.conf exists and has the proper permissions:

    ~# chmod 640 /etc/named.conf
    ~# chown root.named /etc/named.conf
    
  • Verify that the file /etc/named.caching-nameserver.conf exists and has the proper permissions:

    ~# chmod 640 /etc/named.caching-nameserver.conf
    ~# chown root.named /etc/named.caching-nameserver.conf
    

Important: verify that named runs in a chrooted environment:

~# grep ROOTDIR /etc/sysconfig/named
ROOTDIR=/var/named/chroot

In this case, the path to all named files begins with "/var/named/chroot":

~# ls -l /var/named/chroot/etc/named.caching-nameserver.conf
~# ls -l /var/named/chroot/etc/named.conf

Related Articles

BIND DNS server on CentOS 5.6

Additional information

What Operating System is the best for PBA-S-managed Name Servers?

DNS zones are not synced to PBA-S-managed nameservers

Registering Name Server Managed via SSH

400e18f6ede9f8be5575a475d2d6b0a6 caea8340e2d186a540518d08602aa065 70a5401e8b9354cd1d64d0346f2c4a3e 624ca542e40215e6f1d39170d8e7ec75

Email subscription for changes to this article
Save as PDF