• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • 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.

Why change the subdomain structure?

ToolBox

Basic Pleskian
Why change the subdomain structure?

the 10.4.4 plesk dns server structure, each subdomain has it's own dns zone.
It is very difficult to manage secondary dns server.

The server managed by plesk, it's dns zone must be duplicate to secondary dns server.
But now, subdomain zone file is separately, so i have to make zone on secondary dns server before create subdomain on plesk.

When I create a subdomain to a server that is managed by plesk, how you can cooperate with an external secondary DNS server?
 
Back
Top