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

problem whit DNS

Reset the DNS entries back to the default so that the NS record is pointing to the main DNS server, qualityprices.com. It's my understanding that you want the Plesk server to be the master and the others as secondary. So, set it back to the defaults.

If you're gonna use secondary name servers and you plan to pull zone information, then you have to tell Plesk to allow this. However, if they pull it, then they're pulling the information as it's entered and that's the ip addresses too.

Also, enter ns.qualityprices.com as the primary DNS server in your registrar, and then enter your secondary servers in the registrar as well. If you allow zone transfers, then make sure that if you use anything outside that network, that you assign pubic ip addresses to Plesk.

Then, use the tools at www.dnsreport.com to check for errors, such as missing NS records.
 
Back
Top