- Newest
- Most votes
- Most comments
Although what is stated in the re:Post Agent is correct 100% but my issue was something totally different.
while using the whois.com to check my domain i noticed that the domain was in a Status called Client Hold which means that i need to verify my contact email in order to use the domain.com smoothly.
What led me to suspect the domain registration is that i was able to access the application on the EC2 via the public Elastic IP4, meanwhile Google/dig is not reporting NXDOMAIN while in the browser DNS_PROBE_FINISHED_NXDOMAIN.
Resolution:
- from the Route53 console go to Domains > Registered Domains / click on the desired domain (if you have many)
- you will find at the top a Message prompting to verify your email. click on it, verify your email, wait for 10 min max, then your domain will be active.
sometimes the problem is very simple.
When you register a domain in Route 53, there are several key steps needed to ensure it resolves properly. Based on your situation, here are the most likely causes and solutions:
- Nameserver Mismatch: The most common issue is that the nameservers in your domain registration don't match those in your Route 53 hosted zone. You need to:
- Check the nameservers listed in your Route 53 hosted zone for domain.com
- Verify that these same nameservers are configured in your domain registration settings
- If there's a mismatch, update the nameservers in the domain registration to match those in the hosted zone
-
Hosted Zone Configuration: Ensure you've created a public hosted zone for your domain. When you register a domain, it doesn't automatically create the hosted zone.
-
DNS Propagation Time: DNS changes can take up to 24-48 hours to fully propagate globally. This is because DNS resolvers cache information and only request updates periodically.
-
Security Group Configuration: Verify that the security group for your EC2 instance allows inbound traffic on the necessary ports (typically 80 and 443 for web traffic).
-
TTL Values: Check the Time-to-Live (TTL) values on your DNS records. Lower TTL values can help speed up propagation, but some resolvers might cache information for longer periods.
To troubleshoot further:
- Use the
digornslookupcommand to query your domain against one of the AWS nameservers directly - For example:
nslookup domain.com ns-xxx.awsdns-xx.com(using one of your assigned nameservers) - This should return your Elastic IP if the Route 53 configuration is correct
If after checking these settings and waiting 24-48 hours you still have issues, you may want to contact AWS Support, which is available at no additional charge for domain registration issues.
Sources
Route 53 domain not showing in DNS | AWS re:Post
Route 53 domain dns not propagating | AWS re:Post
DNS Propagation Issues with Domain Registered in Route 53 - No Propagation After 48 Hours | AWS re:Post
Domain registered on Route 53 not resolving properly | AWS re:Post
Relevant content
- asked 3 years ago
- asked a year ago
- asked 4 years ago
