Description of problem: I cannot start the named [bind] service because /etc/named.conf file was not found. Version-Release number of selected component (if applicable): bind-9.3.3-6.fc6
Could you please attach an output from /var/log/messages? (when named fails to start)
Created attachment 141549 [details] /var/log/messages
Regardless of the "won't start" behavior (which I'm not seeing on my system, because I also installed caching-nameserver, which seems to provide a working named.caching-nameserver.conf file), a default named.conf ought to be created, but is not. It is expected behavior for all services to have a starting configuration file, and historically one has always existed after installation of bind from every prior version of the RPM I've used. I guess this is related to this changelog entry: - fix bug 176388: named.conf is now never replaced by any RPM Seems that named.conf is now also never created by any RPM.
Ok, I noticed that the messages file provided by reporter does not contain the information requested. So I've replicated his situation, and the result is: [root@localhost ~]# service named start Locating //etc/named.conf failed: [FAILED] Nothing happens in /var/log/messages, because the initscript detects the lack of named.conf before it even gets a chance to try to start. Installing the bind-chroot package changes the error from the initscript, but only to reflect the /var/named/chroot//etc/named.conf path.
(In reply to comment #2) > Created an attachment (id=141549) [edit] > /var/log/messages good point, have you installed the caching-nameserver package? If not you have to create /etc/named.conf by hand or by some utility like system-config-bind.
(In reply to comment #3) > Regardless of the "won't start" behavior (which I'm not seeing on my system, > because I also installed caching-nameserver, which seems to provide a working > named.caching-nameserver.conf file), a default named.conf ought to be created, > but is not. It is expected behavior for all services to have a starting > configuration file, and historically one has always existed after installation > of bind from every prior version of the RPM I've used. I've checked the bind package and there isn't any default /etc/named.conf so if you don't install caching-nameserver named will not start. The question is if it's right...
I've added a notice about it to bind init script.
$ rpm -ql caching-nameserver /etc/named.caching-nameserver.conf /etc/named.rfc1912.zones /usr/share/doc/caching-nameserver-9.3.3 /usr/share/doc/caching-nameserver-9.3.3/Copyright /usr/share/doc/caching-nameserver-9.3.3/rfc1912.txt /var/named/localdomain.zone /var/named/localhost.zone /var/named/named.broadcast /var/named/named.ca /var/named/named.ip6.local /var/named/named.local /var/named/named.zero The package caching-nameserver do not contain any /etc/named.conf file. Perhaps, /etc/named.caching-nameserver.conf is an alternative one. As a novice, it is tough for me to create a configuration file rather than editing one. For example, httpd.conf enables common configurations with default values. Other rarely used configurations are commented out. Thus I can spend more time on using a program rather than configuring it.
Right, /etc/named.caching-nameserver.conf should be used instead of /etc/named.conf and it's designed to work out of the box...
Sure, this works, but it's just not historically sound, and it confuses users. People expect a default configuration file, named what the configuration file is usually named (in this case named.conf). It feels like a pretty major packaging policy change, without a very good reason for it. It also assumes that the only tools people are using to edit the BIND configuration are the ones provided by Fedora. All other tools expect a named.conf file.
(In reply to comment #10) > Sure, this works, but it's just not historically sound, and it confuses users. > People expect a default configuration file, named what the configuration file is > usually named (in this case named.conf). It feels like a pretty major packaging > policy change, without a very good reason for it. > > It also assumes that the only tools people are using to edit the BIND > configuration are the ones provided by Fedora. All other tools expect a > named.conf file. Okay, so how do you propose to solve it?