`.IN` domain joharstore.in returns NXDOMAIN — Route 53 not delegated by registry

Based on your description, it appears there's a nameserver mismatch between your Route 53 configuration and what's being recognized by the .IN registry. This is a common issue that can cause NXDOMAIN errors.

When you register a domain with Route 53, AWS automatically creates a hosted zone and assigns four nameservers to it. For proper resolution, the nameservers in your domain registration settings (glue records) must exactly match those in your Route 53 hosted zone.

Since you're able to query your domain directly against one of the AWS nameservers (dig joharstore.in @ns-647.awsdns-16.net), but global resolution fails, this strongly suggests the domain's nameserver delegation at the registry level is incorrect or missing.

To resolve this issue:

1. Verify that the NS records in your Route 53 hosted zone match exactly with the nameservers listed in your domain registration settings in Route 53.
2. If they don't match, update the nameservers in your domain registration settings to match those in your hosted zone.
3. If they do match, you may need to force a resync by resetting the nameservers to their default settings.
4. Be aware that DNS changes can take up to 48 hours to propagate globally, though it often happens much faster.

If after checking these settings and waiting for propagation you still experience issues, you should contact AWS Support through the Account and Billing section, which is available at no additional charge for domain registration issues.
Sources
Domain resolve failing, SERVFAIL error | AWS re:Post
Route 53 domain not showing in DNS | AWS re:Post
recover hosted zones | AWS re:Post
Route 53 domain dns not propagating | AWS re:Post