Route 53 hosted, AWS Registered domain not resolving after 18+ days...

Hello.

If you perform name resolution of the domain's NS record and A record as shown below, name resolution will be successful.
So I think the problem is with the Amplify code and/or configuration, not with Route53.

dig denverdev.net ns

; <<>> DiG 9.18.18-0ubuntu0.22.04.1-Ubuntu <<>> denverdev.net ns
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17701
;; flags: qr rd ad; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;denverdev.net.                 IN      NS

;; ANSWER SECTION:
denverdev.net.          0       IN      NS      ns-1433.awsdns-51.org.
denverdev.net.          0       IN      NS      ns-2006.awsdns-58.co.uk.
denverdev.net.          0       IN      NS      ns-394.awsdns-49.com.
denverdev.net.          0       IN      NS      ns-732.awsdns-27.net.

;; Query time: 120 msec
;; SERVER: 172.27.16.1#53(172.27.16.1) (UDP)
;; WHEN: Mon Jun 09 07:58:46 JST 2025
;; MSG SIZE  rcvd: 184

dig denverdev.net

; <<>> DiG 9.18.18-0ubuntu0.22.04.1-Ubuntu <<>> denverdev.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45854
;; flags: qr rd ad; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;denverdev.net.                 IN      A

;; ANSWER SECTION:
denverdev.net.          0       IN      A       99.84.141.105
denverdev.net.          0       IN      A       99.84.141.127
denverdev.net.          0       IN      A       99.84.141.60
denverdev.net.          0       IN      A       99.84.141.118

;; Query time: 120 msec
;; SERVER: 172.27.16.1#53(172.27.16.1) (UDP)
;; WHEN: Mon Jun 09 07:58:49 JST 2025
;; MSG SIZE  rcvd: 108

If you access it with the culr command as shown below, you will see that a 404 error occurs.

curl denverdev.net -LI
HTTP/1.1 301 Moved Permanently
Server: CloudFront
Date: Sun, 08 Jun 2025 23:07:57 GMT
Content-Type: text/html
Content-Length: 167
Connection: keep-alive
Location: https://denverdev.net/
X-Cache: Redirect from cloudfront
Via: 1.1 1e36ff29d50bfea32de46ffa3cc40d7e.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: NRT57-P10
Alt-Svc: h3=":443"; ma=86400
X-Amz-Cf-Id: JKWYejyZ8J8eEDTtbiuOO1H7hZTPRGAqHC242hTdrSQVHi2SgYKXhA==

HTTP/2 302 
location: https://www.denverdev.net/
date: Sun, 08 Jun 2025 23:07:58 GMT
x-cache: Miss from cloudfront
via: 1.1 5e3bb6e3ae118b4e8f87b8a1818321ca.cloudfront.net (CloudFront)
x-amz-cf-pop: NRT57-P10
alt-svc: h3=":443"; ma=86400
x-amz-cf-id: O8TaHA0gjHeHt3kuYY9aMsPNZQQ8Bel7kwBiiwkyrTXLh4KEXXVjcQ==

HTTP/2 404 
date: Sun, 08 Jun 2025 23:07:58 GMT
server: AmazonS3
x-cache: Error from cloudfront
via: 1.1 a92159aa2721c217f1de94bdff848352.cloudfront.net (CloudFront)
x-amz-cf-pop: KIX56-C2
alt-svc: h3=":443"; ma=86400
x-amz-cf-id: ygNL7H1fGvVrTDhU37pE-IXnTOYMAZh_sdkQIfcKNt33LzIA2ybzFQ==

You can contact AWS Support via the following URL.
If it’s a problem with Route53 domain name resolution, you can probably contact them for free, but if it’s a technical problem with Amplify, you’ll need to sign up for a paid plan.
https://console.aws.amazon.com/support

Based on your description, there are several potential reasons why your domain isn't resolving properly despite being registered with AWS and hosted in Route 53 for over 18 days.

First, check if your domain might be suspended due to non-verification. AWS requires domain registrations to be verified via an email that's sometimes sent to your spam folder. If you didn't verify the domain within the required timeframe, it could have been suspended.

Second, ensure that the nameservers (NS records) in your domain registration settings exactly match those provided by Route 53 for your hosted zone. This is a common issue - the NS records in your Route 53 hosted zone must match the glue records for your domain. You can check this by:

1. Opening your Public Zone in Route 53
2. Making note of the 4 NS Records
3. Verifying these match the nameservers in your domain registration settings

Third, verify your DNS record configuration. Make sure you have properly set up the necessary records (like A records or CNAME records) to point to your Amplify application. Even if Amplify shows a successful deployment, without proper DNS configuration, your domain won't resolve to your application.

If you're getting a SERVFAIL error when using nslookup or dig commands, this typically indicates an issue with DNS resolution or server configuration.

As a troubleshooting step, you could try creating a new hosted zone and updating your domain's nameservers to point to this new zone, which has helped others with similar issues.

If these steps don't resolve your issue, you can open a case with AWS Support under "Account and billing" which can be done free of charge for domain-related inquiries.
Sources
Domain Registration Successful but Unable to Resolve Domain | AWS re:Post
Domain resolve failing, SERVFAIL error | AWS re:Post
Route 53 DNS stopped propagating | AWS re:Post
My domain is unavailable on the internet - Amazon Route 53
my domain is not working with aws. | AWS re:Post