Bind won't start: /etc/named.conf

Imri Zvik imriz at
Tue Sep 28 21:49:35 UTC 2010

What are you trying to achieve? An empty named.conf file means named will
use defaults for everything, and will probably just work out-of-the-box (as
a simple resolver) so you should give more information about the goal and
problem (including log entries, troubleshooting data etc.).

-----Original Message-----
From: Dotan Cohen [mailto:dotancohen at] 
Sent: Tuesday, September 28, 2010 11:11 PM
To: bind-users at
Subject: Bind won't start: /etc/named.conf

I have just installed bind on a CentOS 5 machine but it won't start
without /etc/named.conf:

[root at venus etc]# /etc/init.d/named start
Locating //etc/named.conf failed:
[root at venus etc]# touch /etc/named.conf
[root at venus etc]# /etc/init.d/named start
Starting named:                                            [  OK  ]

Now, a blank named.conf isn't helpful, but I cannot use the named.conf
from another server as a template because it references other files
(specifically /etc/db.cache). What is the "default" named.conf file
for CentOS? I have tried to google for it but have not been able to
find something that works.

Thanks in advance.

Dotan Cohen
bind-users mailing list
bind-users at

More information about the bind-users mailing list