route53 problem

You mention a new subdomain, this is the correct process for creating one in Route 53 https://repost.aws/knowledge-center/create-subdomain-route-53

It could be as simple as propagation taking a while when the new domain is provisioned. If you do a whois on your domain - use the whois command or go to https://who.is/ - what does it show? Can you dig the new A-record and CNAME that you have created in Route 53 - again use the dig command or use https://toolbox.googleapps.com/apps/dig/

Also, as AWS is resolving it okay but the rest of the world isn't, can you ensure that you're setting this up in a Route 53 Public Hosted Zone and not a Private Hosted Zone.

Last thing (which it probably isn't, but worth ruling out) if you are using DNSSEC then try disabling it. You can always re-enabe it again later once you get things working https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-configuring-dnssec-disable.html

1. Check DNS Propagation Delay:

DNS changes can take 24-48 hours to propagate globally due to ISP caching. Wait for this timeframe before testing again.

2. Verify Record Configuration: => Login to the AWS Management Console and navigate to Route 53.

=>Select your hosted zone.

=>Double-check the following records

A record for your domain Ensure the domain name and the public IP address of your EC2 instance are accurate.

CNAME record for your subdomain: Make sure the subdomain name points to the correct EC2 subdomain (including any periods at the end).

3. Use External Tools:

While AWS tools might show successful resolution, try tools like dig or host on external servers to confirm global propagation. 4. Check EC2 Instance Health:

Use Route 53 Health Checks to monitor your EC2 instance. If the instance is unhealthy, it can cause timeouts during nslookup. Refer to this guide for setting up health checks: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/health-checks-types.html

for more information you can contact AWS Support team : https://aws.amazon.com/contact-us/