DNS TXT not replicating

Hello.

I tried resolving the NS record name from my home, but it failed.

dig ns aquaone.me

; <<>> DiG 9.18.39-0ubuntu0.24.04.5-Ubuntu <<>> ns aquaone.me
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 25608
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; EDE: 9 (DNSKEY Missing): (no SEP matching the DS found for aquaone.me.)
;; QUESTION SECTION:
;aquaone.me.                    IN      NS

;; Query time: 100 msec
;; SERVER: 10.255.255.254#53(10.255.255.254) (UDP)
;; WHEN: Thu Jun 11 20:27:27 JST 2026
;; MSG SIZE  rcvd: 89

I've been checking the propagation status of DNS records on the following website, but it appears they've only propagated to a limited number of countries.
https://whatsmydns.me/#NS/aquaone.me

Are the following NS records correct for the Route53 hosted zone?

ns-2030.awsdns-61.co.uk
ns-571.awsdns-07.net
ns-1150.awsdns-15.org
ns-354.awsdns-44.com

DNS propagation delays for TXT records can occur for several reasons. Here are the most common issues and how to address them:

Check Your TTL Value The Time to Live (TTL) setting on your TXT record determines how long DNS resolvers cache the information. If you recently created or modified the _atproto TXT record, DNS resolvers may still be caching old information (or the absence of the record) based on the previous TTL value. To speed up propagation:

• Set your TTL to 60 seconds or less in your Route 53 hosted zone
• Wait for the old TTL period to expire before the new value takes full effect

Verify Name Server Configuration Ensure that your domain registrar is pointing to the correct Route 53 name servers. You can check this by:

• Comparing the name servers listed in your Route 53 hosted zone with those configured at your domain registrar
• If they don't match, update your registrar to use the four name servers provided by Route 53
• Note that name server changes can take 24-48 hours to fully propagate

Clear DNS Caches If your record values aren't consistent across different DNS providers, try clearing your local DNS cache and testing from different networks or locations.

Verify Record Configuration Double-check that your TXT record is properly formatted in Route 53. For TXT records, ensure there's a blank space between multiple parts if applicable, and verify that values aren't incorrectly wrapped in quotation marks.

Since you're seeing inconsistent propagation (some providers see it, others don't), this strongly suggests either a TTL-related caching issue or a name server mismatch. Start by verifying your name servers match between your registrar and Route 53, then ensure your TTL is set to 60 seconds or less.
Sources
Troubleshoot DNS resolution issues for records in Route 53 public hosted zones | AWS re:Post
Troubleshoot DNS propagation issues that occur after a domain transfer. | AWS re:Post
I changed DNS settings, but they haven't taken effect - Amazon Route 53