After re-attaching DNS node, PPA panel shows the error:
Error message or request description : Destination host 'vmsdc1intpkl02' (#5), IP '18.104.22.168' : Internal error: /usr/sbin/rndc /usr/sbin/rndc reload 4.3.2.IN-ADDR.ARPA. failed with code 1 saying: STDOUT: '' STDERR 'WARNING: key file (/etc/rndc.key) exists, but using default configuration file (/etc/rndc.conf) rndc: 'reload' failed: not found
Re-attaching DNS node corrupts the DNS records in
To restore broken domain zone for domains it is necessary to remove DNS hosting from each domain temporarily and add it back.
Follow the steps below to restore broken/missing domains zones on DNS servers in CP:
Log into CP
Switch to the DNS Management > DNS Zones tab
Choose the problem domain
Switch to DNS tab
Click the Change DNS Hosting to External button
On the next step click the 'Finish' button - DNS hosting will be removed for the domain (domain will be removed from managed DNS servers)
Click the 'Change DNS Hosting to Internal' button in domain properties
On the next step select the desired subscription with DNS Hosting resource from drop-down list
Click 'Next' and 'Finish'
Wait until corresponding background tasks which update managed name servers are processed in Task Manager. For Bind-based DNS servers tasks are named like 'Update named ns1.provider.com(#1)', where ns1.provider.com is the hostname of DNS server and #1 is its ID in database.
Note: Keep in mind that it may take couple of minutes while PPA processes tasks.
As a result of the actions above DNS hosting will be removed for the domain and will be added back - domain zone will be recreated using data from database. All existing DNS records (including ones manually created) will stay in touch because PPA does not remove them from database when DNS hosting is being removed for the domain.