1 Answer
- Newest
- Most votes
- Most comments
1
What's the TTL (time-to-live) for the NS records for the domain when it was on the other registrar? It's usually 172800 seconds (48 hours) but it may be more.
Also, if the domain is using DNSSEC then try disabling it and see if that improves things. After you get the propagation issue straightened out you can re-enable it later.
Relevant content
- asked 9 months ago
- asked 5 years ago
- asked 2 years ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
Hi Steve, Thanks for your reply. Yes the TTL was 48 hours for old NS records. No DNSSEC was enabled there. It has been >48 hours since the last change on Route53. I am wondering if enabling DNSSEC on Route53 would help? I am hoping that 72 hour cycle would make sense. 20 hours more to go, but I am not sure if that will work either. Please help.
The actions I took 48 hours before were - I recreated hosted zone and made sure NS records match with the ones mentioned in registered domain.
Do a whois on the domain and note the name servers https://lookup.icann.org/en/lookup
Alternatively, dig the domain and note the NS records https://toolbox.googleapps.com/apps/dig/
And select the Registered Domain in Route 53 and note the Name servers https://us-east-1.console.aws.amazon.com/route53/domains/home
And the NS records in the Hosted Zone https://us-east-1.console.aws.amazon.com/route53/v2/hostedzones
If all of these align in all cases then it should be okay. If anything is out-of-line then fix it up.
At this point I would think about raising a support call with AWS to get help with this. Even if you're on a Basic Support plan (which would preclude you from raising a support call most of the time) you can still do so under Account and Billing -> Service: Billing -> Category: Domain Registration Issue
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-contact-support.html