Generating Etc Rndc.key Bind

Generating Etc Rndc.key Bind Rating: 8,8/10 3047 votes

What and how to use RNDC? RNDC stands for Remote Name Daemon Control. It is a name server control utility in bind. This name server control utility allows command line administration of the named service both locally and remotely. The rndc.key file defines a default command channel and authentication key allowing rndc to communicate with named on the local host with no further configuration. Running rndc-confgen-a allows BIND 9 and rndc to be used as drop-in replacements for BIND 8 and ndc, with no changes to the existing BIND 8 named.conf file. Previously, rndc.key was generated during package installation (via `rndc-confgen -a` command), but this feature was removed in RHEL 6.1 because users reported that installation of bind package sometimes hung due to lack of entropy in /dev/random. CentOS 6.3でBINDを起動しようとすると、以下のメッセージを出して固まる。 Generating /etc/rndc.key:解決策はここにあるように. Fixing the BIND (named) Service Bug – Generating /etc/rndc.key. I must admit, I have never had this bug for a very loong time. I thought It must have been fixed.

So I have an /etc/rndc.conf which has both the key and some other options in it (specifically a default-server pointing at a different IP address than 127.0.0.1).
My problem is that the bind service will always go and create /etc/rndc.key regardless of whether there is an rndc.conf in place. This then generates a warning everytime I invoke an rndc command ...

Generating Etc Rndc.key Bind Code


# rndc reload
WARNING: key file (/etc/rndc.key) exists, but using default configuration file (/etc/rndc.conf)

Generating Etc Rndc.key Bind Key


Bind Generate Rndc Key

Is there any way to stop this? In CentOS 6 I just modified the init script but before I go modifying systemd services in 7, I want to be sure there isn't a more sensible way to do it.