Route53 Hosted Domain Not working

The SERVFAIL error you're seeing indicates there's still an issue with your domain's nameserver configuration. This typically happens when there's a mismatch between the nameservers listed at the registrar level and those in your Route 53 hosted zone.

Here are the likely causes and solutions:

1. Propagation Delay: DNS changes can take up to 24-48 hours to fully propagate globally. Since you only made the changes an hour ago, you may need to wait longer for the changes to take effect.

2. Nameserver Mismatch: Double-check that the nameservers in your domain registration settings exactly match those in your Route 53 hosted zone. You can verify this by:

• Opening your Public Zone in Route 53 and noting the 4 NS Records
• Going to the Registered Domains section in Route 53 and confirming they match

3. Multiple Hosted Zones: If you have more than one hosted zone with the same name (augusta-mail.com), make sure you're using the nameservers from the correct hosted zone.

4. Missing or Incorrect Records: Ensure you've created the necessary DNS records in your hosted zone.

To troubleshoot further:

• Run a whois command to check your registrar-level nameservers and compare them with your hosted zone nameservers
• Verify that all four AWS nameservers are correctly listed in your domain registration
• Clear your local DNS cache to ensure you're not seeing cached results

If the issue persists after 24-48 hours, 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 owned domain is not being resolved | AWS re:Post
Troubleshoot DNS resolution issues for records in Route 53 public hosted zones | AWS re:Post
Resolve website access issues in Amazon Route 53 | AWS re:Post
My domain is unavailable on the internet - Amazon Route 53

When I lookup the name servers for your domain augusta-mail.com.

I see:

% dig -t NS augusta-mail.com.

; <<>> DiG 9.10.6 <<>> -t NS augusta-mail.com.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23963
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;augusta-mail.com.		IN	NS

;; ANSWER SECTION:
augusta-mail.com.	86400	IN	NS	ns1.bdm.microsoftonline.com.
augusta-mail.com.	86400	IN	NS	ns2.bdm.microsoftonline.com.
augusta-mail.com.	86400	IN	NS	ns3.bdm.microsoftonline.com.
augusta-mail.com.	86400	IN	NS	ns4.bdm.microsoftonline.com.

;; Query time: 40 msec
;; SERVER: 80.254.79.7#53(80.254.79.7)
;; WHEN: Mon Sep 29 09:07:38 CEST 2025
;; MSG SIZE  rcvd: 137

This seems to be behaving as expected, if this is the delegation set that you have provided in the AWS Console for your registered domain.