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 ...
# rndc reload
WARNING: key file (/etc/rndc.key) exists, but using default configuration file (/etc/rndc.conf)![Generating Generating](/uploads/1/2/6/0/126044200/615546203.png)
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.
- I've just installed Webmin and created a zone that appears to be correct, since Check BIND returns No errors were found in the BIND configuration file /etc/named.conf or referenced zone files.
- Rndc (8) - Linux Man Pages. Rndc: name server control utility. Index of rndc man page. Read rndc man page on Linux: $ man 8 rndc. Use key-file as the key file instead of the default, /etc/rndc.key. The key in /etc/rndc.key will be used to authenticate commands sent to the server if the config-file does not exist.
- I'm installing bind on a clean Centos 6.3 system. In previous versions that would work like a charm, but now I get Generating /etc/rndc.key when trying to start bind.
- I've just installed Webmin and created a zone that appears to be correct, since Check BIND returns No errors were found in the BIND configuration file /etc/named.conf or referenced zone files.
Rndc 鍵は rndc コマンドを実行するために必要となるが、RHEL6 では bind パッケージ導入後、サービスを起動しようとすると以下の rndc 鍵関連で停止する。.
Generating Etc Rndc.key Bind Code
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 Pdf
# rndc reload
WARNING: key file (/etc/rndc.key) exists, but using default configuration file (/etc/rndc.conf)
![Generating Generating](/uploads/1/2/6/0/126044200/615546203.png)
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.