Why does bind not ship a named.conf configuration file in RHEL5 or newer?
Environment
- Red Hat Enterprise Linux (RHEL) 5 or newer
Issue
- The bind package owns the
named.conffile but this file is not installed. Why is this? - Why is there not named.conf file after bind is installed?
- Missing named.conf file
Resolution
This is normal for this package, it gets shipped with ghost config files and provide an example in its respective docs directory to customize. The rationale is that you need to customize the config as there is no sane default one to deploy. We do want to mark it as a config file to ensure we own the config file.
This behaviour is also the upstream behaviour. Please see https://www.isc.org/software/bind/faq for details, question "Isn't "make install" supposed to generate a default named.conf?"
Root Cause
This was changed with the introduction of RHEL5, see the following bugzilla for more details: BZ 234508.
Diagnostic Steps
[root@redhat bind-9.3.6]# rpm -qc bind | grep named.conf
/etc/dbus-1/system.d/named.conf
/etc/named.conf
[root@redhat bind-9.3.6]# ll /etc/named.conf
ls: /etc/named.conf: No such file or directory
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
