Route53 A record did stop respolve in public domain

Based on your description, it sounds like you're experiencing a DNS resolution issue with your Route 53 domain. This is a common problem that can occur for several reasons.

The most likely cause is a mismatch between the nameservers listed in your domain registration and those in your Route 53 hosted zone. When you register a domain with Route 53, it doesn't automatically ensure that the nameservers in the domain registration match those in your hosted zone, especially if you've created a new hosted zone manually.

To troubleshoot this issue:

1. Verify that the nameservers listed in your domain registration exactly match those in your Route 53 hosted zone. You can check this by:

• Going to the Route 53 console and looking at the nameservers listed in your hosted zone
• Then checking the Registered Domains section in Route 53 to verify the nameservers match

2. If there's a mismatch, update the nameservers in the domain registration to match those in the hosted zone.

3. Check for any "expired" flags on your contact information in the registered domain section, as this can sometimes cause resolution issues.

4. If you've recently made changes or if the domain was automatically renewed, there might be a delay in propagation. DNS changes can take up to 48 hours to propagate globally, though it often happens much faster.

5. If you've deleted and recreated the hosted zone at some point, the new zone would have different nameservers than the original, requiring an update to the domain registration.

The fact that your A record resolves correctly when tested within Route 53 but not externally strongly suggests that the top-level domain's nameservers don't have the correct information about your domain's authoritative nameservers.

If these steps don't resolve the issue, you may need to contact AWS Support for further assistance, as they can help with domain registration issues even on the basic support plan.
Sources
domain algnotes.info registered with AWS Route 53 stopped resolving after automatic renewal | AWS re:Post
Route 53 owned domain is not being resolved | AWS re:Post
Troubleshoot DNS resolution issues for records in Route 53 public hosted zones | AWS re:Post
DNS Propagation Issues with Domain Registered in Route 53 - No Propagation After 48 Hours | AWS re:Post
recover hosted zones | AWS re:Post