• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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