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

Question Limit on serial number - DNS zone changes

phixious

New Pleskian
Server operating system version
AlmaLinux 9
Plesk version and microupdate number
Plesk Obsidian Web Pro Edition Version 18.0.66 Update #2
While attempting to process a migration for 75 subdomains from old hosting to new, I am getting this error:
2647655:678ab66c86ef3 ERR [panel] The limit on serial number changes was reached. No more DNS zone changes can be carried out today.

I was processing this through a small bash script to create the subdomains using "plesk bin subdomain --create ...." when I ran into this problem about 2/3's through my processing batch.

I'm just trying to figure out if I need to worry about this and change some setting to get things created or if I can create all the domains today and then run an update on them for the DNS zone changes tomorrow and have it all fixed?
 
The default serial is built like this yyyymmddxx.

I assume you made 99 changes to the parent domain DNS zone.
 
The default serial is built like this yyyymmddxx.

I assume you made 99 changes to the parent domain DNS zone.
The only thing that I did was performed the given command. Once I got through 50 of the subdomain creations, it started to throw that error with each additional creation.

Can I just create all of the other subdomains and run one final update for all of them to have this be correct or should I wait and only do what ones are possible to complete before running into this limit? It makes the migration take a 24 hour wait that way so.. it is kind of a hinderance but, if that is how it has to be, I will deal with it.

Summary:

Ran "Plesk bin subdomain --create mysub1.domain.com" for the first 50~ domains and then started running into this issue.
Need to finish the migration and just need advice on how to proceed and if I will face any issues if I miss any of the ones that had this error upon creation

Thanks in advance.
 
The limit by default is 98. I am honestly not sure why you would hit it on the ~50 subdomain creation. As a workaround, what I can recommend is to disable "Use the serial number format recommended by IETF and RIPE" in Tools & Settings > DNS Settings > Zone Settings Template. Are you by any chance using Slave DNS Manager?
 
I do not have Primary/Slave DNS setup. I managed to get it all done just by waiting 24 hours and taking care of it that way. It is good to know that I can work around it by modifying the Zone Settings Template though.

Is there a command that I should run after creating them all to re-enable this setting or add it to all of the subdomains that didn't get it if I need to go this route in the future?
 
Back
Top