Resolved DigitalOcean DNS Extension reactivates deactivated domains

[TomBoB]

Username:

TITLE

DigitalOcean DNS Extension reactivates deactivated domains

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk 18.0.56 Update #4 , AlmaLinux 8.8 , DO DNS Ext 1.4.1-350

PROBLEM DESCRIPTION

subscriptions/domains that are deactivated/disabled in the DO DNS extension [because name servers other then DO are used for that domain] reactivate in the extension on any DNS changes in Plesk.

STEPS TO REPRODUCE

Have multiple domains set up. Have the DO DNS extension loaded.
1) DigitalOcean name servers are used for some domains.
2) Different name servers are used for other domains. Example here: xyz.com
Disable/Deactivate in the DO DNS Extension the domains that do not use the DO name servers. Example here: deactivate xyz.com in the DO DNS extension.
Go to xyz.com and change some DNS settings.

ACTUAL RESULT

The domain automatically reactives and all DNS settings are pushed to the DO name servers.

EXPECTED RESULT

domain stays deactivated in the DO DNS extension.

ANY ADDITIONAL INFORMATION

The good thing, this doesn't do harm or break anything.
However having servers with 500+ domains, of which only say 20 use the DO name servers, it becomes a nuisance as soon [due to security cert DNS entry changes] all domains are active again in the DO DNS extension. Result: Huge amounts of unnecessary entries on the DO name servers when only a few should be there.

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug

 

[Peter Debik]

Thank you for the report, I have forwarded it as PPS-15189 to developers.

 

[Peter Debik]

A product issue has been confirmed and will be fixed in a future update of the extension. It can be tracked in the change log by EXTPLESK-5185.

 

[TomBoB]

Please fix this as a matter of high urgency.
DO has changed some policies - It is now a major nuisance to have to constantly monitor the DO account to remove unwanted domains again that pop up on the name servers just because of Lets Encrypt related DNS changes.

 

[Kaspar]

Fixed in latest extension update 1.4.5.

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