DNS Resolution Issue After Domain Transfer to Route 53

Question

Hi everyone,

I recently transferred a domain to Route 53 and updated the A record to point to a new IP address. However, even after making the change, the domain is still resolving to the old IP.

I’ve checked the following:
	•	The A record in Route 53 is correctly updated.
	•	The TTL value is set appropriately.
	•	It has been some time since the change, but the update hasn’t propagated.

Has anyone experienced a similar issue? Are there additional steps I should take to ensure the new record is correctly propagated?

Thanks in advance for any insights!

Lance · Accepted Answer

3.	Go to Route 53 → Registered Domains and update the NS records to match those of your new hosted zone.
	4.	If applicable, remove any references to the old DNS provider from previous records.

Did the trick

re:Post Agent · Answer

The issue you're experiencing is not uncommon when transferring domains or updating DNS records. Even though you've made the changes in Route 53, there are several factors that can affect how quickly these changes propagate across the internet.

First, it's important to understand that DNS propagation can take up to 48 hours to complete globally, although it often happens much faster. During this time, some users may still be directed to the old IP address while others see the new one.

Here are some steps you can take to troubleshoot and potentially resolve the issue:

1. Verify 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.

2. Check the hosted zone: Confirm that you've created a new hosted zone in Route 53 and properly recreated all necessary DNS records, including the updated A record.

3. Review TTL values: While you mentioned checking the TTL, it's worth noting that lower TTL values can help speed up propagation. However, some DNS resolvers may cache information for longer periods.

4. Use DNS lookup tools: Utilize online DNS lookup tools from different locations to verify DNS resolution for your domain. This can help you determine whether the issue is localized or global.

5. Clear local DNS cache: While you can't flush DNS caches globally, clearing the DNS cache on your local machine or network devices might help if your local DNS resolver is still holding onto old records.

6. Check for 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.

7. Monitor DNS health: Consider using Route 53's DNS health checks to monitor the status of your DNS records globally.

If you've verified all these points and are still experiencing issues after 48 hours, it may be worth contacting AWS Support for further assistance with your domain transfer and DNS configuration.

Remember, patience is often key in DNS changes, as the propagation process is not something you can directly control.
      
**Sources**  
[Domain name is not resolving globally after migration | AWS re:Post](https://repost.aws/questions/QUPjH9x4rtSc2T4_-ZeHpnWg/domain-name-is-not-resolving-globally-after-migration)  
[I changed DNS settings, but they haven't taken effect - Amazon Route 53](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/troubleshooting-new-dns-settings-not-in-effect.html)  
[Migrated domain to AWS and DNS not working in many places | AWS re:Post](https://repost.aws/questions/QUqz-4R9dPSzC5nkVHzZOvWg/migrated-domain-to-aws-and-dns-not-working-in-many-places)

DNS Resolution Issue After Domain Transfer to Route 53

Add your answer

Relevant content