/etc/namedb/rndc.key exists ......

root@s5:/etc/namedb # rndc status
WARNING: key file (/etc/namedb/rndc.key) exists, but using default configuration file (/etc/namedb/rndc.conf)
version: 9.9.5 (tetris 1.0beta) <id:>
CPUs found: 8
worker threads: 8
UDP listeners per interface: 8
number of zones: 1
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
recursive clients: 0/0/1000
tcp clients: 0/100
server is up and running
root@s5:/etc/namedb #

Читать дальше →

dns bind

создадим ключ

cd /etc/namedb
touch rndc.key
rndc-confgen >> rndc.conf


в итоге получаем

# Start of rndc.conf
key "rndc-key" {
        algorithm hmac-md5;
        secret "*********IBfA4aVO9*****";
};

options {
        default-key "rndc-key";
        default-server 127.0.0.1;
        default-port 953;
};
# End of rndc.conf

# Use with the following in named.conf, adjusting the allow list as needed:
# key "rndc-key" {
#       algorithm hmac-md5;
#       secret "*********IBfA4aVO9*****";
# };
#
# controls {
#       inet 127.0.0.1 port 953
#               allow { 127.0.0.1; } keys { "rndc-key"; };
# };
# End of named.conf


часть задокументированную переносим в named.conf и убираем #

часть копируем в rndc.key
key "rndc-key" {
        algorithm hmac-md5;
        secret "*********IBfA4aVO9*****";
};


правим далее как обычно сам named.conf
запускаем /usr/sbin/named -u bind

и при rndc status видим «ругань» типа

rndc status
WARNING: key file (/etc/namedb/rndc.key) exists, but using default configuration file (/etc/namedb/rndc.conf)
version: 9.8.1-P1 (tetris 1.0beta)
CPUs found: 4
worker threads: 2
number of zones: 1514
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 4
query logging is OFF
recursive clients: 0/0/10000
tcp clients: 0/1000
server is up and running


у нас последняя версия. просто удалим файл rndc.conf, проблема уйдет.