• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Issue with Slave DNS Manager

Colb

New Pleskian
Hello,

After reading https://devblog.plesk.com/2013/10/slave-dns-and-plesk/ i set up my secondary DNS server.
Everything is fine, the Slave DNS Manager connexion to the slave server is OK but it doesn't create the zones. I can create it manually and then synchronize, but that's not the idea.
Now, when you add a domain in Plesk, a DNS zone is automatically created on the slave server as well as on the master server.

In the logs i see :
Code:
received control channel command 'addzone mydomain.tld { type slave; file "mydomain.tld"; masters { xxx.xxx.xxx.xxx; }; };'
received control channel command 'refresh mydomain.tld'
received control channel command 'addzone mydomain.tld { type slave; file "mydomain.tld"; masters { xxx.xxx.xxx.xxx; }; };'

When i try manually to
Code:
 rndc -c slave.config addzone mydomain.tld
or
rndc -c slave.config addzone mydomain.tld '{ type slave; file "mydomain.tld"; masters { xxx.xxx.xxx.xxx; }; };'
I got
Code:
rndc: slave.config does not exist
It seems the problem is there.

I already did a
chown -R named:named .
in /var/named
 
Last edited:
Do you have lines like

INFO [panel] Executing /usr/local/psa/admin/plib/modules/slave-dns-manager/scripts/slave-dns.php done.

in /usr/local/psa/admin/logs/panel.log ?
 
It looks like extension was not installed correctly. Try to re-install it and check /usr/local/psa/admin/logs/panel.log again.
 
No change.
I reinstalled the extension, and even tryied on a fresh install.
I think i missed something
 
Hey @Colb
The error "rndc: slave.config does not exist" is related to the non existing config path in your CLI execution:
Code:
rndc -c /usr/local/psa/var/modules/slave-dns-manager/slave_10.58.104.114.conf addzone mydomain.tld '{ type slave; file "mydomain.tld"; masters { xxx.xxx.xxx.xxx; }; };'
Where the config file /usr/local/psa/var/modules/slave-dns-manager/slave_10.58.104.114.conf was created by the extension.

I can create it manually and then synchronize, but that's not the idea.
Could you please describe how do you create it and what do you expect?
 
Back
Top