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

DNS zone serial number is 0 after upgrade

H

hectorh

Guest
All the dns zones that existed before the upgrade to 8.6 now have a serial number of 0.

This then is causing the slave DNS servers to reject the zones.

All the new domains added after the upgrade to 8.6 have proper serial numbers.

We have hundreds of domains affected by this, It would take too long to "recreate" each domain at a time.

What is the command to cause Plesk to "update" all the zones at once?

(P.S. I can go into the Plesk DB and update the serial numbers in the DB manually, but that won't update the DNS server)

Thanks,

Hector
 
Just resolved this on one of our servers with a bit of SQL and patience.

USE AT YOUR OWN RISK!

Login to the PSA database. Run this:
Code:
UPDATE `dns_zone` SET `serial_format`='YYYYMMDDNN',`serial`=CONCAT(DATE_FORMAT(NOW(),'%Y%m%d'),'01');

Now login to Plesk, click domains, select all, group operations, turn "OFF" the "DNS zone" option. Save it ("OK"). This may take a while. Click domains again, select all, group operations, turn "ON" the "DNS zone" option. Save it ("OK"). This will take a while, too.
 
Back
Top