• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question 2 Plesk servers as Master and one server as Slave setup

kevinmamaqi

New Pleskian
I have two VPS running obsidian on ubuntu 20.04. I am using them as master DNS servers and running the slave dns manager extensions to point to a third server that has BIND9, being used as a slave. My setup is the following (named.conf) and server 1.1.1.1 works, but 2.2.2.2 doesn't. Am I missing something? Is this even possible?


Code:
key "rndc-key-1.1.1.1" {
    algorithm hmac-md5;
    secret "mysecret1";
};

key "rndc-key-2.2.2.2" {
    algorithm hmac-md5;
    secret "mysecret2";
};

controls {
    inet * port 953 allow { 1.1.1.1; 2.2.2.2; 127.0.0.1; } keys { "rndc-key-1.1.1.1"; "rndc-key-2.2.2.2"; };
};
 
Last edited:
Hi kevinmamaqi,

Have you checked log files on all three servers? Are there any errors or warnings?
This configuration could work but it could cause issues if the same domain is existing on two master servers at the same time because they will overwrite the information on the slave server.
 
Hi AYamshanov,

Which logs should I check? Server 1 (Plesk master) and Bind9 (slave) works well, the problem is that when I add the server 2 (Plesk master2) it doesn't authenticate properly with the slave manager ui. The message is: rndc: connection to remote host closed.

I also noticed that I have a file in BIND9 slave server called rndc.key with the following content:


Code:
key "rndc-key" {
        algorithm hmac-md5;
        secret "mysecret1";
};
 
Back
Top