Route 53 DNS Propagation Issue for www.ai.getpay.click

Your hosted zone appears to be for getpay.click, and you've added a record named www.ai, which Route 53 interprets as: www.ai.getpay.click That is correct in format, but only works if a matching delegation (NS record) exists for ai.getpay.click in the same hosted zone.

The real issue: You do not have a delegation (NS) record for ai.getpay.click inside the getpay.click zone, so Route 53 does not know to look for www.ai.getpay.click as a valid subdomain.

That’s why: ai.getpay.click resolves (probably because it has an explicit A record).

But www.ai.getpay.click returns NXDOMAIN, because there’s no delegation for ai, and no record at the parent zone (getpay.click) telling Route 53 how to resolve deeper subdomains.

Fix: You need to explicitly create a record for www.ai.getpay.click in the getpay.click hosted zone, not as www.ai, but as a fully qualified record:

Step-by-step: Go to your getpay.click hosted zone in Route 53.

Click "Create Record".

Set:

Record name: www.ai.getpay.click (not just www.ai)

Record type: A

Value: 51.24.1.208

TTL: 300 (or your preferred)

Save and wait a few minutes (~1–5 min).

Double Check: Run from any terminal: dig A www.ai.getpay.click @8.8.8.8

If it now returns your IP 51.24.1.208, propagation is complete.

What Not To Do: Do not use just www.ai unless you're managing a separate hosted zone for ai.getpay.click (with its own delegation).

Do not assume that creating ai.getpay.click means you can nest records under it without proper delegation or explicit entries.

Based on the information provided, there appears to be a misunderstanding in how DNS records for subdomains work in Route 53. The issue is likely with how you've configured the record name for your www.ai subdomain.

When you create an A record with the name "www.ai" in the getpay.click hosted zone, Route 53 interprets this as www.ai.getpay.click (which is what you want). However, the way you've described your record configuration suggests there might be an issue with how the record is actually set up.

Here are the most likely causes and solutions:

1. Record Name Format Issue: When creating the A record, you should enter just "www.ai" in the record name field (not the fully qualified domain name). If you entered "www.ai.getpay.click" in the record name field, Route 53 would interpret this as www.ai.getpay.click.getpay.click, which is incorrect.

2. Nameserver Mismatch: Although you've verified that the nameservers match between your domain registration and hosted zone, it's worth double-checking that these are exactly the same, character for character. Any discrepancy can cause DNS resolution failures.

3. TTL Considerations: While you've set a 300-second TTL, some DNS resolvers might cache NXDOMAIN responses for longer periods. This could explain why changes aren't being reflected immediately.

4. Record Creation Approach: Try creating the record with a slightly different approach:

• First, create an A record for "ai" pointing to your IP address
• Then, create a CNAME record for "www.ai" pointing to "ai.getpay.click"

This two-step approach sometimes resolves propagation issues with deeply nested subdomains.

5. Verify with Direct Nameserver Query: Test the record by querying one of your Route 53 nameservers directly:

dig www.ai.getpay.click @ns-556.awsdns-05.net

If this returns the correct IP but general queries don't, it confirms a propagation issue rather than a configuration problem.

If after implementing these suggestions the issue persists for more than 48 hours (the maximum typical propagation time), it may be worth considering contacting AWS Support for further assistance, as they can provide more in-depth troubleshooting specific to your account and configuration.
Sources
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 Registration Successful but Unable to Resolve Domain | AWS re:Post
Route 53 DNS stopped propagating | AWS re:Post
Domain resolve failing, SERVFAIL error | AWS re:Post