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

SOA-record set to secondary DNS

I'm now running 12.5.3 and it still is not working properly...
Please advice....
 
Last edited:
As it was promised that it would get a fix I've let this go for a while.
But now it turns out it is still behaving erratically.
The way this is being handled is quite poor.
It is obviously not working as it should, but during reporting it seems as if I'm hitting a brick wall.
The issue at first didn't get an acknowledgement and later it was handled as something of low-priority.

I see this completely different. The Plesk manager is supposed to help me with all the settings I can do.
Now it is, on its own initiative, changing parameters on my setup.
This behaviour is confirmed by other users of Plesk, but still nothing has changed.
It is doing this now almost a year.

I've also waited 4 years for SRV-records to behave as they should (https://talk.plesk.com/threads/srv-records-can.114958/)
Come on Odin, thanks for the nice high resolution icons, but now fix things for the real reason why we have Plesk!!
 
Yes...
A pity why they just don't solve it.
The "workaround" given actually means we're not taken serious.
 
Back
Top