How do I register new SSH-manageable nameserver based on RedHat EL 5/CentOS 5/FedoraCore 5/FedoraCore 6 OS template?

Article ID: 2208 
Last Review: Oct,6 2008
Author: Tarasov Yuri APPLIES TO:
  • HSPcomplete 3.3.x

Symptoms

New nameserver based on RedHat EL 5/CentOS 5/FedoraCore 5/FedoraCore 6 OS template registered in HSPcomplete system have Error status after installation, password was entered correctly.


 

Cause

Bind caching-nameserver configuration file on new RedHat-based distributions (RedHat EL 5/CentOS 5/FedoraCore 5/FedoraCore 6) is now by default /etc/named.caching-nameserver.conf instead of /etc/named.conf as it was in previous OS versions.


Resolution


For new nameservers based on RedHat EL 5/CentOS 5/FedoraCore 5/FedoraCore 6 distributions the following changes should be additionally performed before registration in HSPcomplete system:
  • /usr/sbin/rndc utility on the nameserver have no executive bit set for all:

    # ls -l /usr/sbin/rndc
    -rwxr-x--- 1 root root 21812 Oct 16 09:26 /usr/sbin/rndc

    It is required to allow members of named group to execute this utility:
    # chgrp named /usr/sbin/rndc
  • new nameserver configuration file inside the nameserver VE should be created as /etc/named.conf with the following content:

    options {
            listen-on port 53 { 127.0.0.1; any; };
            directory       "/var/named";
            dump-file       "/var/named/data/cache_dump.db";
            statistics-file "/var/named/data/named_stats.txt";
            memstatistics-file "/var/named/data/named_mem_stats.txt";
            query-source    port 53;
            query-source-v6 port 53;
            allow-query     { any; };
            allow-transfer { none; };
    };
    logging {
            channel default_debug {
                    file "data/named.run";
                    severity dynamic;
            };
    };
    include "/etc/rndc.key";
    controls {
            inet 127.0.0.1 port 953 allow { localhost; };
           };
    view localhost_resolver {
            match-clients      { localhost; };
            match-destinations { localhost; };
            recursion yes;
            include "/etc/named.rfc1912.zones";
    };
    view "external" {
            match-clients      { any; };
            match-destinations { any; };
            recursion yes;

            include "/var/named/named.zones";
    };
  • permissions for /etc/named.conf file should be changed in the following way:
    # chmod 640 /etc/named.conf
    # chown root.named /etc/named.conf
Keywords: nameserver
Subscription for this article changesSubscription for this article changes

Please provide feedback on this article

Did this article help you solve your issue?
Yes
No
Partially
I do not know yet
 
Strongly Agree   Strongly Disagree
  9 8 7 6 5 4 3 2 1
The article is easy to understand
The article is accurate
Additional Comments:
*Please provide us with your email address in case we need to contact you.
captcha *Please type the code you can see.
* - required fields