Applicable to:
- Plesk for Windows
Symptoms
- After changing of the Default Delegation Set in AWS Route 53 and pressing the Sync All Zones button, the new duplicated Hosted Zones are created on AWS side with the name servers from Default Delegation Set
- After changing of the Default Delegation Set, the duplicated Hosted Zone can be also created on AWS side when a new DNS record in Domains > example.com > Hosting & DNS > DNS and pressing the Update button.
Cause
This is the Plesk bug with the ID #EXTPLESK-8995
Resolution
Until the bug will be resolved, in order to restore properly integration between Plesk and AWS Route 53 for all domains, the following workaround can be applied:
The main goal of the workaround below is to move all hosted domains to a single Delegation Set which is currently set as default.
For this please apply the following steps:
1. Go to Plesk > Extensions > My Extensions > Amazon Route 53
2. Press the Sync All Zones button in Mass Management
3. After this, for domains that do not have Hosted Zones on AWS with name servers from currently Default Delegation Set, will be created the the corresponding Hosted Zones on AWS with bunch of name servers from the Default Delegation Set
4. Then for domains that are not using the currently Default Delegation Set, you will be need to set/change NS to the name servers from Default Delegation Set on the DNS Registrar side for corresponding domain
5. After the step №4 will be completed and DNS propagation finished to the newly configured name servers, you could start removing of Hosted Zones from AWS Route 53 for domains that do not have name servers from the Default Delegation Set on AWS Route 53
The changing to a new name servers should not cause a long downtime for domains because there will be simultaneously two Hosted Zones with old and new NS records.
6. To make a final synchronization between Plesk and AWS Route 53, press again Sync All Zones button in AWS Route 53 extension
Comments
Please sign in to leave a comment.