• 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!
  • 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Unable to transfer zone file to slave server

LaneP

New Pleskian
Hi all

We've provisioned a new instance of Plesk on a CloudLinux server. We've installed the Slave DNS Manager extension and configured a slave server. The sync between these two servers is showing as successful in Plesk.

Our issue is that the zone file isn't being transferred to the slave server.

Our "symptoms" are identical to the first three listed in the following support article:
Unable to transfer zone to slave server: zone may fail to transfer to slaves

However, we've triple checked that the secret keys are identical on the slave server in the following files:
- rndc.key
- named.conf

We've also confirmed the directory/file permissions are correct.

Can anyone provide any additional things we should be checking to hopefully resolve this issue?

Thank you kindly.
 
Hi LaneP,

I don't ever configure Slave DNS Manager with Plesk on CloudLinux, but I did it for Plesk and slave DNS server on CentOS with SELinux. If you run a slave DNS server on CentOS with enabled SELinux, you need to tune named_write_master_zones setting (named_selinux(8) - Linux man page):

Code:
# getsebool named_write_master_zones
named_write_master_zones --> off
# setsebool -P named_write_master_zones 1
# getsebool named_write_master_zones
named_write_master_zones --> on
#

I am not sure but hope it can help you.
 
Hi AYamshanov

Thank you for your response. We're not running SELinux but this lead me to another post of yours that contained information that resolved the issue.

Post:
Zone don't get created or modified on Slave · Issue #3 · plesk/ext-slave-dns-manager

Cause:
The zone is added to the running name server, and it is added to a configuration file. The filename is a hash of the view name with extension .nzf. 'named' need write permission for create files in work directory. By default work directory without write permission for 'named'.

Resolution on Slave DNS Server:
# ls -la /var/ | grep named
drwxr-x---. 6 root named 4096 Jan 13 14:52 named
# chmod g+w /var/named
# ls -la /var/ | grep named
drwxrwx---. 6 root named 4096 Jan 13 14:52 named
# service named restart
- Resync all DNS zones in Slave DNS Manager on Plesk Server

Note we're running named in a chroot environment so the paths are different than above. Looks like this is an issue only for CloudLinux/CentOS servers running Plesk.

Thank you for your help. It's very much appreciated.
Lane.
 
Back
Top