• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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 (http://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