Migrated domain to AWS and DNS not working in many places

Looks like you have the wrong GLUE records on your domain vs your Route53 Name Servers. When you create a Domain in route53 it automaticlly creates a zone. You may have created a new zone which will have different NS records

Your current defined name servers are

ns-1032.awsdns-01.org
ns-1915.awsdns-47.co.uk
ns-353.awsdns-44.com
ns-575.awsdns-07.net

Which I believe are incorrect.

In Route53, you need to check your name servers (NS) and update them https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html#domain-name-servers-glue-records-adding-changing

Based on the information provided, it appears that you're experiencing issues with DNS propagation after migrating your domain to AWS. This is a common problem that can occur during domain transfers or DNS changes. Here are a few potential reasons and solutions for your situation:

1. Propagation delay: DNS changes can take up to 48 hours to propagate globally. However, since it's been over a week in your case, this is likely not the primary issue.

2. Nameserver configuration: Ensure that the nameservers (NS records) at your domain registrar exactly match those provided by AWS Route 53. Any discrepancy can prevent proper DNS resolution.

3. Hosted zone setup: Verify that you've created a new hosted zone in Route 53 and properly recreated all necessary DNS records. If the previous owner deleted the hosted zone associated with the domain, you need to set this up correctly.

4. Glue records: Make sure you've updated the glue records to point your domain to the new Route 53 nameservers.

5. TTL values: Check the Time-to-Live (TTL) values on your DNS records. Lower TTL values can help speed up propagation, but some resolvers may cache information for longer periods.

6. Multiple hosted zones: If you have multiple hosted zones with the same name, ensure you're updating the correct one and that the domain registration is using the correct nameservers.

To troubleshoot:

1. Use tools like dig or nslookup to verify that the new NS records are propagating correctly.
2. Double-check all DNS records in your Route 53 hosted zone for accuracy.
3. Verify that your domain registration details are correct and that you've confirmed any necessary verification emails from ICANN.

If you've verified all these points and are still experiencing issues, it may be worth contacting AWS Support under the "Account and Billing" category for further assistance with your domain transfer and DNS configuration.

Sources
transferred domain name not recognized after waiting for about a week | AWS re:Post
my domain is not working with aws. | AWS re:Post
DNS not propagating after domain migration from one aws account to another | AWS re:Post
I changed DNS settings, but they haven't taken effect - Amazon Route 53