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

On Sat, Oct 2, 2010 at 11:16, Imri Zvik im...@inter.net.il wrote: What does the logs say? Thanks, Imri, the logs complain about /etc/db.cache. I copied /etc/db.cache from the ns1 server to the ns2 server and bind stopped complaining. Is the server chrooted or not? no And I think you want to

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: [r...@venus etc]# /etc/init.d/named start Locating //etc/named.conf failed: [FAILED] [r...@venus etc]# touch /etc/named.conf [r...@venus etc]#

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

On Tue, Sep 28, 2010 at 23:49, Imri Zvik im...@inter.net.il wrote: 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