You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a number of dns servers up using docker-bind but the last two that I've set up (after the latest build back in May 2020) I continually run into the following issue after setting up rndc for a fresh container with a new zone:
/root@dns:/# rndc flush
WARNING: key file (/etc/bind/rndc.key) exists, but using default configuration file (/etc/bind/rndc.conf)
rndc: connection to remote host closed
This may indicate that
* the remote server is using an older version of the command protocol,
* this host is not authorized to connect,
* the clocks are not synchronized,
* the key signing algorithm is incorrect, or
* the key is invalid.
This isn't a significant issue as bind can just be restarted, but wondering if there's a quick fix for it (other than reverting to an older container release).
Thanks!
The text was updated successfully, but these errors were encountered:
I have a number of dns servers up using docker-bind but the last two that I've set up (after the latest build back in May 2020) I continually run into the following issue after setting up rndc for a fresh container with a new zone:
This isn't a significant issue as bind can just be restarted, but wondering if there's a quick fix for it (other than reverting to an older container release).
Thanks!
The text was updated successfully, but these errors were encountered: