Route 53 owned domain is not being resolved

Based on your description, it sounds like you're experiencing a nameserver mismatch between your Route 53 domain registration and your hosted zone. This is a common issue that prevents domains from resolving properly.

When you register a domain with Route 53, it doesn't automatically create a hosted zone or set up the correct nameservers. You need to ensure that the nameservers in your domain registration settings exactly match those provided by Route 53 for your hosted zone.

Here's how to fix this issue:

1. Open your Public Zone in Route 53 and make note of the 4 NS Records assigned to your hosted zone.

2. Go to the Registered Domains section in Route 53 and verify that the nameservers listed for your domain exactly match those in the hosted zone.

3. If there's a mismatch (which appears to be the case since you're seeing GoDaddy nameservers), update the nameservers in the domain registration to match those in the hosted zone.

The fact that you're seeing GoDaddy nameservers suggests that either:

• The domain was previously registered with GoDaddy and the nameservers weren't updated after transfer to AWS
• The domain was registered with AWS but the nameservers were manually set to GoDaddy's

After updating the nameservers, it may take up to 24-48 hours for the changes to fully propagate globally, though it often happens much faster with Route 53.

If after checking these settings and waiting for propagation you still have issues, you might need to contact AWS Support through the Account and Billing section, which is available at no additional charge for domain registration issues.
Sources
Route 53 domain not showing in DNS | AWS re:Post
DNS Propagation Issues with Domain Registered in Route 53 - No Propagation After 48 Hours | AWS re:Post
Route 53 hosted, AWS Registered domain not resolving after 18+ days... | AWS re:Post
Domain Connection Issue: NXDOMAIN Error | AWS re:Post