Skip to content

EU domain DNS information not propagating / gandi.net information incomplete

0

Hi, After 48H of my domain transfer (EU) which apparently AWS makes via gandi,net is not propagating. whois from gandi.net lists only 3 of the 4 DNS records showing up in Route53 Whatsmydns show correct ( as per gandi) DNS records in 2 countries in 2 continents and dead everywhere else.

Any chance I am doing something incorrectly ? or I should just wait and wait....

dig returns SERVFAIL at my local machine...and failing to propagate NX records I am out of email.

Thanks.

JC

asked a year ago161 views

2 Answers
0

Based on your description, you're experiencing DNS propagation issues after transferring your EU domain to AWS Route 53 (via Gandi.net). This is a common issue that can occur during domain transfers, but there are several things to check:

  1. Nameserver Mismatch: There appears to be a discrepancy between the nameservers shown in Route 53 and those registered with Gandi.net. This mismatch is likely causing the propagation issues. Ensure that all four Route 53 nameservers are properly registered with Gandi.net.

  2. Glue Records: Check if your domain's glue records match your Route 53 nameservers. Incorrect glue records can cause DNS resolution problems.

  3. Propagation Time: While DNS changes typically propagate within 48 hours, some resolvers may cache information longer. The fact that you're seeing correct records in some locations but not others suggests partial propagation.

  4. Verify Hosted Zone Configuration: Double-check that your Route 53 hosted zone is correctly set up with all necessary DNS records (A, CNAME, MX, etc.).

  5. Multiple Hosted Zones: Ensure you don't have multiple hosted zones for the same domain, which could cause confusion.

To resolve this issue:

  1. Verify that the nameservers in your domain registration settings match exactly with those in your Route 53 hosted zone.

  2. If you created a new hosted zone after transferring the domain, make sure you're using the nameservers from that zone.

  3. Consider lowering TTL values on your DNS records to speed up propagation.

  4. The SERVFAIL error you're seeing with dig suggests there might be a configuration issue with your DNS records.

Unfortunately, there's no way to force immediate global DNS propagation. If after verifying all settings you're still experiencing issues after another 24-48 hours, consider contacting AWS Support for further assistance with your specific case.
Sources
Route 53 domain dns not propagating | AWS re:Post
Domain transferred to route53 but not propagated after five days | AWS re:Post
Migrated domain to AWS and DNS not working in many places | AWS re:Post
Troubleshoot DNS propagation issues that occur after a domain transfer. | AWS re:Post

answered a year ago

0

Automated answer not human reviewed as stated in the banner. Misinterprets my question. Let's if I manage to get to a human.

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.