• 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 does not synchronize

TorbHo

Regular Pleskian
We bulk-changed DNS ip adresses directly through phpmyadmin (search and replace).
psa -> dns_recs -> val
and
psa -> dns_recs -> displayVal

After that we used "plesk repair dns" to synchronize the new ips with bind.

If we do a dnslookup on the primary DNS server everything seems to be fine.

The Secondary DNS doesn't seem to synchronize the new ips. We don't have direct access to the secondary DNS Server. Do we have to change something in addition, so that the new zones are transfered to the secondary DNS?
 
I'm guessing plesk repair dns didn't update the serial numbers.

Every DNS zone has a serial number, if this number doesn't change, then changes aren't propagated. Every time a change is made, ensure this number is incremented by one so that other name servers see a new zone is available.
 
I'm guessing plesk repair dns didn't update the serial numbers.

Every DNS zone has a serial number, if this number doesn't change, then changes aren't propagated. Every time a change is made, ensure this number is incremented by one so that other name servers see a new zone is available.

Thank you. That worked.

After changing value in: psa -> dns_zone -> serial + "plesk repair dns"

the secondary DNS started to synch.

For the next time: is there a Plesk build-in solution that bulk-changes the DNS ips and the serial, too?
 
Back
Top