Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plesk not synchronizing with route53 #54

Open
umarkhan207322405 opened this issue Sep 30, 2020 · 2 comments
Open

Plesk not synchronizing with route53 #54

umarkhan207322405 opened this issue Sep 30, 2020 · 2 comments

Comments

@umarkhan207322405
Copy link

I created hosted zones using delegation sets in Route53 for my domains in plesk. I installed Route53 extension in Plesk and and when I performed a synchronization from plesk, hosted zones were created in route53 and had different NS records for each zone. please assist me on this issue

@ayamshanov
Copy link
Member

Hi umarkhan207322405,

I created hosted zones using delegation sets in Route53 for my domains in Plesk.

There are two possible ways:

  • Create a delegation set in Plesk/Route53 extension. The extension will use them by default.
  • If you pre-configure other NS in Plesk and want to use exactly them in synchronization with Route53 service, you need to enable a checkbox "Manage NS and SOA records" under authorization form.

@umarkhan207322405
Copy link
Author

First I migrated hosted zones from one aws account to another and recreated those hosted zones tho have the delegation set. I then installed the route53 extension and which displayed the delegation set. I made it default and proceeded with migrating the domain from one aws account to another, when It was finished, I synced thru Mass management and the zones were created while I was hoping for the domains to sync with existing hsoted zone in route 53.

PS I do have Manage NS and SOA records turned on

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants