IPv6 Nameserver Monitor
Mobile carriers, large CDNs, and a growing share of consumer ISPs serve traffic over IPv6 first or IPv6-only. A nameserver without an AAAA record can't be reached from those networks — and DNS resolution failures cascade into everything else. This check confirms each of your nameservers has IPv6.
What we check
We fetch the zone's NS records, then for each nameserver hostname we query its AAAA records. A nameserver passes if it returned at least one AAAA record.
Why it matters
IPv6-only resolvers are a real and growing population. If your authoritative nameservers don't all have AAAA records, every cold lookup from those resolvers either fails or falls back to a more distant translator, adding latency and a dependency on infrastructure you don't control.
Most managed DNS providers (Cloudflare, Route 53, Google Cloud DNS) publish AAAA on every nameserver by default. A failure here usually points at an outdated NS record list rather than a missing AAAA on the provider's side.
Status outcomes
Every nameserver has at least one AAAA record.
Some nameservers have AAAA records and some don't.
None of the nameservers expose IPv6.
The zone has no NS records.
How to fix
Add AAAA records to the nameserver hostnames missing one, or move the zone to a provider that publishes AAAA on its nameservers. Confirm the new records are visible from a public resolver (dig AAAA ns1.example.com) before declaring the fix done.