• 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 DNS Syncing from Plesk Obsidian to Digital Ocean corrupting today with domain name listed twice.

Hi everyone,

Just for history, there were done two different fixes and the same time and from two teams :)
  • The DO team has fixed DO API. It means the old version of the DigitalOcean DNS extension works as previously.
  • The Plesk team has fixed the DigitalOcean DNS extension to avoid similar issues with API in the future.
Code: 
Changes
  1.3.3 (8 April 2022)
  [*] Internal improvements.
 
You must log in or register to reply here.

Similar threads

E
Question Does 1 License cover 2 Digital Ocean Droplets?
Replies
2
Views
3K
Ed3000
E
T
Resolved Digital Ocean DNS extension doesn't sync MX records TTL
Replies
2
Views
2K
AYamshanov
AYamshanov
JohnnyRobert
Issue VPS Server is stuck with the initial Domain Name
Replies
6
Views
7K
Armina
A
mangaldeepdey
Question Use Plesk as Master DNS
Replies
1
Views
2K
xicomen
X
C
Unable to create A DNS record with underscore in Plesk: The specified domain name is not valid. You need to specify a valid domain name like domain.co
Replies
6
Views
6K
scsa20
scsa20
Back
Top