- Newest
- Most votes
- Most comments
Based on the information you've provided, it seems you're experiencing an issue with DNS resolution for your Route 53 hosted domain. This situation is unusual, especially given that it was working for over a week before suddenly stopping. Here are some potential causes and steps to troubleshoot:
-
Nameserver Mismatch: Ensure that the nameservers listed in your domain's registration settings exactly match those provided by Route 53 for your hosted zone. Any discrepancy can cause DNS resolution failures.
-
Hosted Zone Configuration: Verify that you're working with the correct hosted zone, especially if you have multiple zones with similar names. Sometimes, changes might be made to the wrong zone.
-
TTL and Propagation: Although you mentioned it was working for a week, check the Time-to-Live (TTL) values on your DNS records. Lower TTL values can help speed up propagation if you've made recent changes.
-
DNSSEC: If DNSSEC is enabled, ensure it's correctly configured. Misconfigurations can lead to NXDOMAIN responses.
-
Route 53 Service Issues: While rare, check the AWS Service Health Dashboard for any ongoing issues with Route 53.
-
Record Type and Configuration: Double-check that your wildcard record is correctly formatted and of the appropriate type for your needs.
-
Domain Transfer or Expiration: Ensure your domain hasn't expired or isn't in the process of being transferred, which could affect DNS resolution.
To troubleshoot:
-
Use dig or nslookup against Route 53's authoritative nameservers directly to bypass any local DNS caching issues.
-
Review your hosted zone in the Route 53 console, ensuring all records are present and correctly configured.
-
If possible, try creating a new hosted zone and updating your domain's nameservers to point to this new zone.
-
Check if there are any AWS limits you might have hit, although this is unlikely if other domains in the same account are working.
If these steps don't resolve the issue, it may be worth contacting AWS Support for further assistance, as they can provide more in-depth troubleshooting specific to your account and configuration.
Sources
Route 53 DNS Not Propagating | AWS re:Post
DNS Propogation seems to have stalled. | AWS re:Post
Migrated domain to AWS and DNS not working in many places | AWS re:Post
I changed DNS settings, but they haven't taken effect - Amazon Route 53
As I was following AI's instructions to delete current hosted zone and make a new one, I noticed that domain was suspended due to non-verification. Notification email had gone to spam folder and I didn't see it (rather didn't know I had to look for it).
So, it is resolved.
Relevant content
- asked 2 years ago
- asked 2 years ago
- asked 4 months ago
