Why my dns domain does not point to my ec2 instance

0

I transfer my registered domain from another aws account. I created hosted zone record to my instance public ip correctly but I still cannot access my website via my domain?

asked 19 days ago35 views
2 Answers
0

When you transfer a domain between AWS accounts and find that it's not pointing to your EC2 instance as expected, there are several potential reasons for this issue:

  1. Nameserver mismatch: After transferring the domain, the nameservers associated with your domain registration may not match the nameservers of the Route 53 hosted zone in your new AWS account. This mismatch can prevent proper DNS resolution.

  2. Propagation delay: DNS changes can take up to 48 hours to propagate globally. However, if it's been longer than that, this is likely not the primary issue.

  3. Incorrect hosted zone setup: Ensure that you've created a new hosted zone in Route 53 and properly recreated all necessary DNS records, including the A record pointing to your EC2 instance's public IP.

  4. Glue records: Make sure you've updated the glue records to point your domain to the new Route 53 nameservers.

  5. 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.

To resolve this issue:

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

  2. Double-check all DNS records in your Route 53 hosted zone for accuracy, especially the A record pointing to your EC2 instance's public IP.

  3. Use DNS lookup tools to check if your domain is resolving correctly and if the changes are propagating.

  4. Ensure your EC2 instance's security group allows incoming traffic on the necessary ports (typically 80 for HTTP and 443 for HTTPS).

  5. If you're using a web server like Apache, make sure it's configured to listen on your domain name.

If after checking these items the issue persists, you may want to contact AWS support for further assistance, especially since this involves a domain transfer between AWS accounts.
Sources
Migrated domain to AWS and DNS not working in many places | AWS re:Post
DNS error after transferring domain from one AWS account to another | AWS re:Post
domain name not resolving to a site hosted in ec2 windows server | AWS re:Post

profile picture
answered 19 days ago
0

Verify that the nameservers listed in your domain registration settings exactly match those provided by the Route 53 hosted zone. How can i check if my name server match ? There are 4 name servers: ns-791.awsdns-34.net ns-1652.awsdns-14.co.uk ns-427.awsdns-53.com ns-1497.awsdns-59.org

And in dns management the record: Value ns-791.awsdns-34.net. ns-1652.awsdns-14.co.uk. ns-427.awsdns-53.com. ns-1497.awsdns-59.org.

Is that missing . At the end?

answered 19 days 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.

Guidelines for Answering Questions