How to integrate primary Plesk DNS server with secondary Slave DNS server?
The integration can be performed using Slave DNS Manager extension available in Extensions Catalog in Plesk: Plesk > Extensions > install Slave DNS Manager > Add Slave > specify Slave DNS IP Address
Visit Plesk Administrator's Guide for instructions on setting up a secondary DNS.
Use one of the following Plesk extensions:
Note: If the Slave server has Plesk installed, there is no need to install the Slave DNS Manager extension.
Perform the following steps:
Create the same domains in both Master and Slave Plesk servers
Warning: The same domains should exist on both master and slave Plesk servers. It prevents DNS data from getting corrupted.
Change DNS to Slave mode on Slave server side in Domains > example.com > DNS Settings > Switch to Slave
Click Add Record
Specify the IP address of the primary (master) DNS server
How often are the zones synced?
Hello @Abraham Monrroy!
Zones are synced between master and slave DNS servers in 2 conditions:
1. When DNS zone is changed on the master DNS server, master sends notifies to all slaves.
2. In the SOA record of the zone, there is a "refresh" parameter (in seconds):
# nslookup -type=SOA example.com
origin = sns.dns.icann.org
mail addr = noc.dns.icann.org
serial = 2018112865
refresh = 7200
retry = 3600
expire = 1209600
minimum = 3600
Every time this refresh period is expired, slave DNS server connects to master DNS server and refreshes the zone.
The refresh period can be changed in Plesk in Tools & Settings > DNS Template > SOA Records Template > Refresh interval.
I am using Plesk on Windows server. On this server Plesk is running with MS DNS. If i want to deploy external DNS slave server with Plesk as Master DNS. Shall i change Plesk MS DNS with BIND first? OR Slave DNS manager extension is enough to deploy external slave DNS.
It is ok to use MS DNS as a master.
This plugin is not working at all, in fact it is messing up all provisioning of plesk subscriptions. The command issues to RNDC from the plugin is wrong. the error I get is:
/usr/sbin/rndc -b "xxx.xxx.xxx.xxx" -s "xxx.xxx.xxx.xxx" -p "953" -y "rndc-key" -c "/usr/local/psa/var/modules/slave-dns-manager/slave_xxx.xxx.xxx.xxx.conf"
the -y switch actually says "rndc-key" not the actual key supplied to the config. - this basically hangs the server while RNDC waits for a response.
How do we fix that?
Hello @Sean Kimball,
In most cases there are 2 causes of the issue:
The 1 one is that the port 953 is filtered.
More information on this matter can be found here: Cannot setup slave DNS server using Slave DNS extension
The 2 cause is that integration configuration is not added to slave DNS server.
I recommend you to check if the same rndc-key can be found in /usr/local/psa/var/modules/slave-dns-manager/slave_xxx.xxx.xxx.xxx.conf and /etc/named.conf on slave DNS server.
More information on this matter you can also find here:
In case if it does not help, please create a request to Plesk Technical Support: How to submit a request to Plesk support?
We have 5 cPanel DNS only nodes that are currently integrated with cPanel.
If we integrate Slave DNS with our Plesk servers will this extension destroy the current records that are currently in place?
Or will it only write/change/delete records that are on itself only?
Hello 4Web Business,
Slave DNS Manager uses the rndc utility to manipulate the configuration so the records are modified based on the logic of this utility. Also, it depends on the slave server's configuration.
Please sign in to leave a comment.