[Global Outage] Authoritative nameservers responding with NXDOMAIN (RCODE 3) for all zones

[IliaBebebe]

Summary

Since around September 10, 2026, all authoritative nameservers for dynv6 (ns1.dynv6.com, ns2.dynv6.net, ns3.dynv6.net) are responding with NXDOMAIN (RCODE 3, AA=1) to all DNS queries across all zones (including dynv6.net, v6.rocks, v6.navy, and all user subdomains).

Because these responses carry the Authoritative Answer flag (AA=1), global recursive resolvers (Google DNS 8.8.8.8, Cloudflare 1.1.1.1, ISP resolvers) negative-cache the failure, leading to a complete resolution outage for all dynv6 domains worldwide.

Diagnostic Evidence

1. TLD Delegation is Intact

Querying .net TLD servers (a.gtld-servers.net) confirms delegation to:

• ns1.dynv6.com (95.216.144.82)
• ns2.dynv6.net (5.45.100.251)
• ns3.dynv6.net (159.69.43.243)

2. Querying Authoritative Nameservers Directly

All 3 authoritative nameservers are reachable on UDP and TCP port 53, but immediately reply with empty NXDOMAIN:

Server: 95.216.144.82 (ns1.dynv6.com)
Query: dynv6.net (type A) -> RCODE: 3 (NXDOMAIN), AA: 1, AN: 0, NS: 0, AR: 0
Query: v6.rocks (type A)  -> RCODE: 3 (NXDOMAIN), AA: 1, AN: 0, NS: 0, AR: 0
Query: <any_zone>         -> RCODE: 3 (NXDOMAIN), AA: 1, AN: 0, NS: 0, AR: 0

Raw DNS header flags: 0x8503 (QR=1, Opcode=0, AA=1, TC=0, RD=0, RA=0, Z=0, RCODE=3).

3. Current Service Status

• The main web application at https://dynv6.com is reachable.
• community.dynv6.com fails TLS handshake (tlsv1 alert internal error).
• Users began seeing 500 errors and total DNS resolution loss around September 10, 2026 (see also Is dynv6 service completely down? #40).

Suspected Root Cause

The DNS server daemon is running and accepting queries, but has 0 zones loaded in memory (likely due to a database connection failure, backend zone sync breakdown, or failed zone cache reload).

Could the maintainers please check the DNS daemon logs and database connection on the nameservers? Thank you!