• 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.

Slave DNS Manager - Still tries to sync zones that are switched off in Plesk

Chris1

Regular Pleskian
Hello,

I have recently started using the slave DNS manager in the Plesk extension library. I've found that even for DNS zones that are switched off in Plesk, failed sync/transfers still try to take place between the slave and master. Why is this so?

Shouldn't turning the DNS functionality off in Plesk remove the zone from the slave DNS server?

When a domains DNS functionality is turned off, it removed the zone info from the master, but no command is issued to remove it from the slave??

Domain that is trying to sync/transfer: example.com
Plesk/Master server: 111.11.11.111
Slave DNS: 222.222.22.222

Code:
May  6 08:51:39 ns2 named[1178]: zone example.com/IN: refresh: unexpected rcode (REFUSED) from master 111.11.11.111#53 (source 0.0.0.0#0)
May  6 08:51:39 ns2 named[1178]: zone example.com/IN: Transfer started.
May  6 08:51:40 ns2 named[1178]: transfer of 'example.com/IN' from 111.11.11.111#53: connected using 222.222.22.222#53166
May  6 08:51:40 ns2 named[1178]: transfer of 'example.com/IN' from 111.11.11.111#53: resetting
May  6 08:51:40 ns2 named[1178]: transfer of 'example.com/IN' from 111.11.11.111#53: connected using 222.222.22.222#35948
May  6 08:51:40 ns2 named[1178]: transfer of 'example.com/IN' from 111.11.11.111#53: failed while receiving responses: REFUSED
May  6 08:51:40 ns2 named[1178]: transfer of 'example.com/IN' from 111.11.11.111#53: Transfer completed: 0 messages, 0 records, 0 bytes, 0.055 secs (0 bytes/sec)
 
Last edited:
It seems that DNS zones are not being deleted off the slave DNS server if a domain is deleted or if DNS is disabled for a domain.

I tested this by setting up the domain example.com and deleting it. The DNS zone for this domain is still on the slave DNS server.

Is there a directive I need to set in /etc/named.conf to allow the deletion of zones by the slave DNS manager?
 
I ran another test by setting up the domain example2.com and then removed it from the Plesk panel whilst watching /var/log/messages and I got the following:

May 9 09:53:53 ns2 named[1178]: received control channel command 'delzone example2.com'
May 9 09:53:53 ns2 named[1178]: zone example2.com removed via delzone

It appears it has removed the config for example2.com from /var/named/3bf305731dd26307.nzf but hasn't actually removed the zone file. Why isn't it removing the actual zone file?

/var/named/example2 still exists.
 
Back
Top