- Newest
- Most votes
- Most comments
Hello from AWS,
Thanks for posting this query, I can understand that for cases where incorrect DNS records are added the DNS verification fails, and upon re-creation you get a new set of DNS records. Your current approach while managing the the DNS records with an external provider is correct. We would need to delete the existing CNAME records (like the old CloudFront distribution) of the associating domain from the DNS provider and wait for sometime for the DNS to propagate. Then, in the Amplify Console, delete the domain association for the same. After some time, add the required domain again in the Amplify Console and update the records (Actions >> View DNS records) provided by Amplify to your DNS provider. Once the records are added, kindly wait for some time for the Domain to get activated as the DNS propagation takes some time.
We regret the inconvenience caused due to this issue, and as you have already raised a feature request with our team, please be assured that they take customer feedback seriously and would work on improving the service.
Meanwhile, as a workaround you may also choose to leverage Route53 as your DNS service, as Amplify will automatically manage the DNS records for you which would limit the misconfigurations. Please refer below documentation to learn more about the configurations for the same.
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/MigratingDNS.html https://docs.aws.amazon.com/amplify/latest/userguide/to-add-a-custom-domain-managed-by-amazon-route-53.html
Relevant content
- asked 3 years ago
- Accepted Answerasked 23 days ago
- asked 2 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago