2 Answers
- Newest
- Most votes
- Most comments
0
It may just be an issue with re update time of the DNS Systems. Can you please do the following?
- Check the TTL (time-to-live) value set on the records. If it is very high, it may be taking a long time for the cached data to be renewed by other DNS Servers
- Make sure there are no other NS records for the domain configured elsewhere, such as the previous registrar or DNS provider. Extra NS records can cause caching issues.
- Try clearing the DNS cache on your local machine/network. On Linux/Mac you can run
sudo killall -HUP mDNSResponder. On Windows open command prompt as Administrator and typeipconfig /flushdns. - Wait longer than the TTL value before checking from other DNS servers. It can take time for changes to propagate everywhere depending on the TTL.
- Check for any errors when importing the zone file using the AWS CLI or API. Import failures could cause issues.
- Verify the records are configured correctly within Route 53. You can use the
digornslookupcommands to query the Route 53 nameservers directly.
TTL on new records doesn’t dictate how long they propagate across dns servers . Just how long they are cached before asking from them again from the Name servers.
0
Make sure your domain registrar level name servers and the Route 53 hosted zone name servers match. You can find the four Route 53 name servers listed in the Hosted zone details section of your R53 hosted zone.
The exact same name servers must be in your domain registration. This is mentioned as Step 7 in the Route 53 documentation [1].
Relevant content
- Accepted Answerasked 5 years ago
- asked a year ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
Can you supply any screen shots? You could have entered the CNAMES wrong or your NS records are incorrect