This extension integrates Plesk with DigitalOcean DNS service, a highly available and scalable DNS web service which you can use as an external DNS service for your domains. The extension automatically synchronizes the DNS zones from Plesk to DigitalOcean DNS (but not vice versa).

Features

• Easily deploy and synchronize all DNS zones on DigitalOcean DNS.
• Remove all DNS zones information from DigitalOcean DNS.
• A, AAAA, CNAME, MX, TXT, NS, SRV, CAA records are supported.
• DigitalOcean DNS Service is free.
• You will have three redundant slave DNS-servers after sync.
• If you want, you can deploy Plesk anywhere and host your DNS zones on DigitalOcean DNS.
• Easily authenticate to your DigitalOcean account by using OAuth2.

Learn More about DNS on DigitalOcean.

Note: To use this extension, you need to have an account at https://www.digitalocean.com

1.4.8 (14 October 2025)

• [*] Security improvements.

1.4.7 (12 July 2024)

• [*] OAuth API authorization has now been deprecated. Only API token authorization can now be used.

1.4.6 (13 May 2024)

• [*] Security improvements.

1.4.5 (23 April 2024)

• [-] The extension no longer activates the DigitalOcean DNS service for the local DNS zone if it is changed. (EXTPLESK-5185)

1.4.4 (05 April 2024)

• [-] The extension now works more stable and no longer shows PHP warnings. (EXTPLESK-5385)

1.4.3 (01 April 2024)

• [-] The extension no longer crashes with the “Declaration of Plesk\Api\Client::request … must be compatible …” error. (EXTPLESK-5375)

1.4.2 (12 December 2023)

• [-] The extension now works more stable and no longer shows PHP warnings. (EXTPLESK-5227)

1.4.1 (2 November 2023)

• [-] The extension no longer crashes with the “Grant "League\OAuth2\Client\Grant\AuthorizationCode" must extend AbstractGrant” error. (EXTPLESK-5147)

1.4.0 (1 November 2023)

• [-] Custom TTL values for individual records are now correctly synchronized with the DigitalOcean DNS service. (EXTPLESK-2272)

1.3.11 (20 July 2023)

• [*] Internal improvements.

1.3.10 (27 April 2023)

• [-] The extension again correctly opens the main page with the list of domains. (EXTPLESK-4579)

1.3.9 (24 April 2023)

• [-] The extension now correctly handles situations when the rate limit on requests to the DigitalOcean API per hour and/or per minute was exceeded in Plesk. (EXTPLESK-4502)

1.3.8 (07 March 2023)

• [*] Internal improvements.

1.3.7 (24 February 2023)

• [*] Internal improvements.

1.3.6 (23 February 2023)

• [-] The extension now shows the actual status of DNS zones. (EXTPLESK-4374)

1.3.5 (23 January 2023)

• [*] Internal improvements.

1.3.4 (3 January 2023)

• [*] Added a warning that indicates that an access token to DigitalOcean no longer meets the latest security requirements. On March 31, the support of legacy access tokens will be discontinued. If you see such warning on the main page of DigitalOcean DNS, generate a new access token and upload it in the extension.

1.3.3 (8 April 2022)

• [*] Internal improvements.

1.3.2 (8 November 2021)

• [*] Extension icon is now consistent with all other Plesk icons. (EXTPLESK-2472)

1.3.1 (7 June 2021)

• [-] Expired OAuth2 access tokens are now automatically refreshed and no longer prevent the extension from syncing DNS records. (EXTPLESK-2693)
• [-] The "Invalid authorization token. Unable to authenticate you" error is no longer shown after successful OAuth2 authorization. (EXTPLESK-2687)

1.3.0 (12 March 2021)

• [+] The extension now shows a warning if a custom backend script is not properly configured and offers to configure it if necessary.
• [+] A link to the extension was added to the left menu in Power User mode.
• [*] Updated links to the documentation.

1.2.4 (26 February 2021)

• [-] Exceeding 200 domains no longer blocks the extension functioning and does not lead to the API rate limit issue. (EXTPLESK-2450)

1.2.3 (8 February 2021)

• [-] The extension again correctly syncs Plesk NS records for vanity and branded nameservers with the DigitalOcean DNS service. (EXTPLESK-2403)

1.2.2 (18 Jan 2021)

• [+] DNS records of Plesk domains can now be resynced with DigitalOcean DNS.
• [*] Significantly improved the extension's performance.
• [-] The DigitalOcean DNS extension now shows a warning if some DNS records were not synced. (EXTPLESK-1852)

1.2.1 (01 Jun 2020)

• [*] Synced locale languages supported by the extension.

1.2.0 (28 Apr 2020)

• [*] It is now possible to authorize the extension using DigitalOcean API tokens as well as OAuth2.
• [*] NS records for vanity DNS servers ("ns1.yourdomain.com" instead of "ns1.digitalocean.com") are now correctly synchronized from Plesk to DigitalOcean.
• [-] Changes made to the TTL values of DNS zones in Plesk are now correctly synchronized to DigitalOcean. (EXTPLESK-1677)
• [-] CAA records created in Plesk are now correctly synchronized to DigitalOcean. (EXTPLESK-1745)

1.1.5 (24 Dec 2019)

• [-] Synchronizing a domain's DNS zone with DigitalOcean DNS now correctly creates SRV records in DigitalOcean DNS. (EXTPLESK-753)
• [-] Newly created domain aliases are now automatically synced with DigitalOcean DNS. (EXTPLESK-1037)
• [-] On Plesk for Windows servers, it is now possible to open a subscription's page from the main extension's page. (EXTPLESK-1516)

1.1.4 (14 Nov 2019)

• [*] Changed the extension's icon to better fit visually among other icons in Dynamic List view.

1.1.3 (22 May 2019)

• [-] Sync of DNS zones between DigitalOcean DNS and Plesk no longer occasionally fails with the “SOA records are not eligible for deletion” error. (EXTPLESK-894)

1.1.2 (16 Apr 2019)

• [-] Sync of DNS zones between DigitalOcean DNS and Plesk no longer fails with the "name already exists" error. (EXTPLESK-832)

1.1.1 (15 Mar 2019)

• [*] Updated the authorization token necessary for the extension to operate correctly. If you used the extension earlier than version 1.1.1, you may face issues with existing domains activated in DigitalOcean DNS.

  How do I know if my domains were affected?

  • On the "Overview" tab of the extension, the domains are now marked as "Disabled" under "DigitalOcean DNS Zone".
  • On the "DigitalOcean Authorization" tab of the extension, you see the "Invalid authorization token. Unable to authenticate you" error.

  How can I make my domains and extension operational again?

  Please do the following:

  1. Update the DigitalOcean DNS extension to version 1.1.1 (if it is not done yet).
  2. On the "DigitalOcean Authorization" tab of the extension, click Authorize.

  This will restore the domains and the extension to operation.

1.1.0 (20 Feb 2019)

• [*] Newly created domains are now automatically active in the DigitalOcean DNS.
• [-] In Plesk 17.9, the icons on the "DNS management" tab are now displayed correctly. (EXTPLESK-741)

1.0.4

• [+] Added DigitalOcean OAuth2 support

1.0.3

• [-] Fix the issue when MX record with priority 0 is not synced to DigitalOcean DNS records (EXTCERT-1142)

1.0.2

• [-] Fix the issue when DKIM record has value 'false' in DigitalOcean DNS records (EXTCERT-1023)

1.0.1

• [-] Fix performance issues when logged in under customer or reseller

1.0.0

• [+] Initial release