• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!

Issue Slave dns do not work on some servers

Dmytro

Basic Pleskian
Server operating system version
Plesk Obsidian 18.0.66 #1 Web Host Edition
Plesk version and microupdate number
18.0.66 #1
Hi!

For some reason Slave sync stops working on some servers, on some shows "red circle" time to time.
So for example I see next on extension's page ( Plesk Obsidian 18.0.64 #1 Web Host Edition):

o1GufBq.png


and this on slave in the logs:
Code:
Feb 24 15:34:51 ns1 named[3022563]: rejected command channel message from 9*.***.***.197#48375

After one or few F5 (reload) I see again "green circle".

Another server got "red circles" always, if I'm trying to run:

Code:
/usr/sbin/rndc -b 1***.***.***.225 -s 1**.***.***.208 -p 953 -y rndc-key -c /usr/local/psa/var/modules/slave-dns-manager/slave_1**.***.***.208.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.

and on the Slave's side:

Code:
invalid command from 1**.***.***.225#42397: bad auth

or

Code:
invalid command from 1**.***.***.225#50807: expired

Hope you will help me.
 
For now it seems like time sync issue.
my NTP extension did not work as expected, so I reinstalled it and synchronized time, after that I can't see errors but I will monitor it
 
Back
Top