Question Slave DNS Manager not sync and connect

[Creativados]

Server operating system version

Debian 10.13

Plesk version and microupdate number

Versión 18.0.48

I'm trying to set up my own DNS slave server

I have followed this official guide

Secondary DNS Server

This section describes how to integrate Plesk with an external Linux-based secondary DNS server. The integration can ...

docs.plesk.com

But after configuring everything, the master server doesn't connect to the slave server


/usr/sbin/rndc -b "51.83.2.118" -s "188.165.212.210" -p "953" -y "rndc-key" -c "/opt/psa/var/modules/slave-dns-manager/slave_188.165.212.210.conf" status 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. Error code: 1

 

[IgorG]

The server time is incorrect. It is 1 minute behind the time:

from the Plesk Server:

# date
Mon Jul 4 20:17:17 SAST 2022

from any other Server:

# date
Tue Jul 5 01:18:18 +07 2022

the time sync is disabled as well:

# timedatectl | grep sync
System clock synchronized: no

To resolve the issue, please sync the time between master and slave servers, for example, using the same NTP server.
The following guide may be useful: https://support.plesk.com/hc/en-us/articles/360003099194

 

[Creativados]

Ok my server is in time.

But result is equal

$ date
Wed Nov 30 06:57:26 CET 2022

# date
Wed 30 Nov 2022 06:57:26 AM CET

/usr/sbin/rndc -b "51.83.2.118" -s "188.165.212.210" -p "953" -y "rndc-key" -c "/opt/psa/var/modules/slave-dns-manager/slave_188.165.212.210.conf" status 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. Error code: 1

 

[IgorG]

Make sure that the key in file /etc/bind/rndc.key match the key in /etc/named.conf:

# grep secret /etc/bind/rndc.key
secret "H226I1Ew0yE4j2VyWMaW7A==";

# grep secret /etc/named.conf
secret "H226I1Ew0yE4j2VyWMaW7A==";

 

[Creativados]

Make sure that the key in file /etc/bind/rndc.key match the key in /etc/named.conf:

# grep secret /etc/bind/rndc.key
secret "H226I1Ew0yE4j2VyWMaW7A==";

# grep secret /etc/named.conf
secret "H226I1Ew0yE4j2VyWMaW7A==";

yes is equal

sudo grep secret /etc/bind/rndc.key
secret "XXXXXXXXwBCrGPQaTfJiqw==";

grep secret /etc/named.conf
secret "XXXXXXXXwBCrGPQaTfJiqw==";