DO DNS Extension for Plesk: NS records are reverted / reset after making a change in the master DNS zone


Currently I’m using the Digital Ocean DNS Extension in Plesk. What this basically does is syncing DNS zones from Plesk to DO DNS. See extension here.

In my case, the DO DNS servers act as slave DNS servers (secondary DNS servers), whereas the Plesk’s DNS server acts as primary. In other words: I only have to manage DNS records in Plesk and with the extension changes to the DNS are then being synced to DO DNS.

Also, I’m using vanity nameservers (see here).

Because of the vanity name servers I edited the NS records in DO DNS manually, to have them showing my domain instead of

When a new domain is added, DO DNS creates NS records like this:   IN   NS   IN   NS   IN   NS

…and then after syncing from Plesk to DO, for vanity nameservers, I manually change them to:   IN   NS   IN   NS   IN   NS

Now, the issue I’m facing is this; if I make any change in the DNS zone in Plesk and let that sync, in DO DNS these NS records (and only the NS records) get reverted back to:

Everything else gets synced perfectly, just the three NS records are being ‘reset’. Also I’ve noticed that if I have additional records, e.g. then that one is being deleted in DO DNS (whereas in Plesk it remains). Hence I think the NS records get ‘reset’ when synced.

I’m a very huge fan of the extension because it does so much for me, but not syncing the NS records properly is very inconvenient. Especially when Let’s Encrypt automatically renews SSL-certificates, it adds records to the DNS for verification and then the NS records in DO DNS are, also automatically, reverted back to pointing at as well because this change will trigger the sync as well.

Also it causes differences in the records of the primary and secondary DNS servers, which against the purpose of the extension.

Anyone else having this problem? Is this something for the DO devs to fix?

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.


Since the Plesk DigitalOcean extension v1.2.0 release, it is possible to configure synchronizing NS records in the extension’s settings tab; it allows configuring branded name servers if required.

Changelog for 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 ("" instead of "") 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)

In case anyone runs into the same issue: I got it fixed, although it’s with a temporary workaround for now. Plesk is aware of the issue and they’ll fix it permanently in upcoming updates of the DO DNS Extension for Plesk.

To solve it with the temporary fix, please follow the instructions provided here:

Important note: I have had contact with DO Support about this issue as well and they had advised NOT to use vanity nameservers if you’re using DO’s Load Balancers or Spaces with the domains you want to use vanity nameservers with. In that case you must use DO’s default nameservers to not run into issues with DNS.

Sir,maybe digitalocean DNS doesn’t support slave DNS.And vanity DNS usually need the origin dns’s permission,and if you don’t set vanity DNS properly,it maybe slow the resolve rate.Ask the extension’s creator and digitalocean support team for further view.

Have a nice day.