Error in named configuration

latheesan

Verified User
Joined
Nov 27, 2005
Messages
33
In my DA control panel System Information page, it says Named is stopped. So, i logged in as root and typed the following command :

Code:
[root@server named]# service named start

I received the following error :

Starting named:
Error in named configuration:
zone localhost/IN: loading master file localhost.zone: file not found
_default/localhost/IN: file not found
zone 0.0.127.in-addr.arpa/IN: loading master file named.local: file not found
_default/0.0.127.in-addr.arpa/IN: file not found
[FAILED]

This is what /etc/named.conf looks like :-

Code:
// generated by named-bootconf.pl

options {
        directory "/var/named";
        /*
         * If there is a firewall between you and nameservers you want
         * to talk to, you might need to uncomment the query-source
         * directive below.  Previous versions of BIND always asked
         * questions using port 53, but BIND 8.1 uses an unprivileged
         * port by default.
         */
        // query-source address * port 53;
};

//
// a caching only nameserver config
//
controls {
        inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};
zone "." IN {
        type hint;
        file "named.ca";
};

zone "localhost" IN {
        type master;
        file "localhost.zone";
        allow-update { none; };
};

zone "0.0.127.in-addr.arpa" IN {
        type master;
        file "named.local";
        allow-update { none; };
};

include "/etc/rndc.key";

Can someone help me please? This is a fresh install of DirectAdmin control panel on a new dedicated server i bought and my host is refusing to help me with it, unless i pay them $10 to their tech.
 
Just delete


zone "localhost" IN {
type master;
file "localhost.zone";
allow-update { none; };
};

zone "0.0.127.in-addr.arpa" IN {
type master;
file "named.local";
allow-update { none; };
};

from named.conf
 
it seems my host forgot to install caching-nameserver for me, so i fixed it my self by doing:

yum install caching-nameserver

and it worked
 
See my previous post as to why you may not want to run a caching nameserver.

Jeff
 
Back
Top