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

Question Centralized DNS

BjornO

New Pleskian
Hello all,

I apologize if this has been answered elsewhere, but my searches failed to find the answer I am lookin for.

According to this page, Plesk should have the capability to "(...) build centralized DNS for multiple Plesk servers".

I am looking to deploy multiple Plesk servers and have them all share the same set of DNS. However, I must also be able to move a domain name from Plesk A to Plesk B without zone conflicts or unintended zone deletions. I bring up the latter because, when moving a domain from Plesk A to Plesk B, at some point after the migration, the domain on Plesk A will have to be deleted, and this should of course not affect the zone for the domain.

Documentation on the slave extension does not describe the above scenario, which I would consider to be of major importance in building this centralized DNS. Does anyone have experience with this setup?
 
Back
Top