- Newest
- Most votes
- Most comments
Hi THere
In the Route53 Registered Domains Console, what do you have the Name Servers set to? Currently your name servers appear to be set to ns1.dns-parking.com and ns2.dns-parking.com. Do you want Route53 to be your DNS service as well as the registrar for the domain? If so, you need to move all of your DNS records to the Route53 hosted zone and update your domain nameservers to the name servers listed in tat hosted zone.
Take a look at https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/migrate-dns-domain-in-use.html
Hello,
Please try this solution it will be resolved.
If your domain pasoapasomissions.org hasn’t propagated after following these steps.
Verify NS Records
Your domain's name server records are set to Route 53’s name servers. Check this using your domain.
Check Registrar Settings
Confirm that your domain registrar (where the domain was originally registered) has updated the name servers to Route 53’s.
Review DNS Records in Route 53
Make sure all necessary DNS records EX. A, CNAME, MX, etc. are correctly configured in your Route 53 hosted zone.
If you want more information, please go through the AWS Document Link.
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-transfer-between-aws-accounts.html
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-transfer-to-route-53-status.html
Thanks for the response.
The route53 hosted zone has all the correct information. for SOA, NS and CNAME. These records were set by route53 when I created the zone. There is no A record yet. I cannot complete the domain setup with Amplify until the DNS information has propagated.
I have no access to dns for the domain with hostinger (original registrar) as the domain has been transferred.
I also checked the whois for the domain and it shows the domain is registered with Amazon Registrar, Inc.
Is there something I need to do to beyond creating a hosted zone? Maybe I just need to wait longer than 5 days?
Thank you @Parthasaradi. I missed a step when setting up my domain. I thought all I needed to do was create a hosted zone but there was a step I missed to change the nameservers. Looking into it now.
I have updated my nameservers to the ones in my hosted zone file. Thank you for the help!
Relevant content
asked 2 years ago
- AWS OFFICIALUpdated 3 years ago
My hosted zone has aws nameserver. For example if I query ns-54.awsdns-06.com directly with dig I get:
pasoapasomissions.org. 900 IN SOA ns-1784.awsdns-31.co.uk. awsdns-hostmaster.amazon.com. ( 1 ; serial 7200 ; refresh (2 hours) 900 ; retry (15 minutes) 1209600 ; expire (2 weeks) 86400 ; minimum (1 day) ) pasoapasomissions.org. 172800 IN NS ns-1310.awsdns-35.org. pasoapasomissions.org. 172800 IN NS ns-1784.awsdns-31.co.uk. pasoapasomissions.org. 172800 IN NS ns-54.awsdns-06.com. pasoapasomissions.org. 172800 IN NS ns-975.awsdns-57.net.
Unfortunately I did not lower TTL etc before the transfer :( but it has been 5 days.
Ok. I may be an idiot. I thought if I set the hosted zone correctly that would fix the NS records. I did not notice the "details" of my domain still has the old name servers. I missed a step here. I will check to see what I need to do to point my domain toward aws which I assume will also point toward my hosted zone.
I have updated my nameservers to the ones in my hosted zone file. Thank you for the help!