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 digitalocean.com:
When a new domain is added, DO DNS creates NS records like this:
mydomain.com IN NS ns1.digitalocean.com mydomain.com IN NS ns2.digitalocean.com mydomain.com IN NS ns3.digitalocean.com
..and then after syncing from Plesk to DO, for vanity nameservers, I manually change them to:
mydomain.com IN NS ns1.mydomain.com mydomain.com IN NS ns2.mydomain.com mydomain.com IN NS ns3.mydomain.com
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:
ns1.digitalocean.com ns2.digitalocean.com ns3.digitalocean.com
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. ns4.mydomain.com 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 digitalocean.com 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?
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.×