Zones are not synced via DNS extensions in Plesk and not sure what to do? Our Support Engineers have an easy solution.

At Bobcares, we offer solutions for every query, big and small, as a part of our Server Management Services.

Let’s take a look at how our Support Team is ready to help customers when zones are not synced via DNS extensions in Plesk.

How to fix: DNS Zones are not synced via DNS extensions in Plesk

If you are wondering what to do when the synchronization of every DNS zone via any DNS extension fails, you are in the right place. This scenario also results in the following message in the /var/log/messages file:

node2 named[1591]: zone example.com/IN: zone serial (2018070713) unchanged. zone may fail to transfer to slaves.
node2 named[1591]: client 203.0.113.2#59417 (example.com): query (cache) 'example.com/MX/IN' denied
node2 named[1591]: client 203.0.113.2#33475 (example.com): query (cache) 'example.com/MX/IN' denied

We will also find the slave-dns.php value for DNS Connector in the Plesk database:

# plesk db "select name, value from ServiceNodeConfiguration where value like '%slave-dns.php%';"
+---------------+-----------------------------------------------------------------------+
| name | value |
+---------------+-----------------------------------------------------------------------+
| custom_script | "/usr/local/psa/bin/extension" --exec slave-dns-manager slave-dns.php |
+---------------+-----------------------------------------------------------------------+
1 row in set (0.00 sec)

Furthermore, we may also come across the following message in the /var/log/plesk/panel.log file when Debug mode is set:

DEBUG [util_exec] [5b40802f9e487] Starting: dnsmng --update example.com, stdin:
DEBUG [util_exec] [5b40802f9e487] Finished in 0.27194s, Error code: TRUE, stdout: , stderr:
INFO [panel] All zones registered in Plesk were synchronized with Amazon.

Interestingly, the reason behind this issue is that the Slave DNS Manager is in use rather than a DNS extension as a third-party DNS service backend.

Fortunately, our Support Techs have come up with a resolution for the error:

1. First, log in to Plesk.
2. Then, head to Extensions > My Extensions and remove the DNS extension.
3. Next, reisntall it under Extensions > Extensions Catalog.

According to our Support Engineers, we can switch back to the Slave DNS Manager without having to uninstall the external DNS extension by connecting via SSH and executing this command:

# plesk db "update ServiceNodeConfiguration set value='"/usr/local/psa/bin/extension" --exec slave-dns-manager slave-dns.php' where name='custom_script';"

[Looking for a solution to another query? We are just a click away.]

Conclusion

To sum up, our skilled Support Engineers at Bobcares demonstrated what to do when zones are not in sync via DNS extensions in Plesk.