• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Resolved Plesk main domain nameserver issues

Rowan

New Pleskian
So have example.com as a main domain registered with only some glue records at my registrar as following:
ns1.example.com
ns2.example.com
ns1.fire.example.com
ns2.fire.example.com

And my plesk server is registered as fire.example.com with two nameservers and unique ip's:
ns1.fire.example.com
ns2.fire.example.com

However since some days both ns1.example.com and ns2.example.com dissapeared from all the dns queries whilst they still are configured within the dns of my fire.example.com server.

Am I missing something? Did a recent update broke my setup?

With thanks,
 
Resolved: One of the nameservers didn't contain the same DNS causing a loop of empty and filled DNS
 
Back
Top