The September 8, 2026 Patch Tuesday fixes nine remote code execution flaws in Windows DNS Server, including CVE-2026-69730, a CVSS 9.8 use-after-free triggerable with a single forged packet. Patch the servers running the DNS role first and segment port 53 before a public exploit appears.
On October 11 2026 the DNSSEC root Key Signing Key moves from KSK-2017 to key tag 38696 (KSK-2024), and the old key is retired in January 2027. Operators of validating resolvers must confirm tag 38696 is installed before the cutover, or their DNS resolution will fail wholesale with no network symptom.
The Iranian Cavern C2 framework has added a module that queries DNS to choose between a direct HTTPS channel and a Google Apps Script relay, plus another that turns Microsoft 365 calendars into a dead-drop. For network detection, indicator blocklists are no longer enough: you have to watch for anomalous DNS queries and abuse of legitimate services.
The Human-Centered Computing Foundation has filed its application with ICANN for the .self top-level domain, a namespace designed for self-hosted, human-centered projects. Behind the symbol, the real question is what a domain name can actually guarantee — and whether .self will serve self-hosters or mark them as targets.
Pi-hole v6 and AdGuard Home 0.107.77 are both thriving in 2026, but the comparison has shifted. Native encrypted DNS, per-client rules, and built-in parental controls make AdGuard Home the clear choice for new deployments. If you’re starting today, the gap isn’t close.
As of 2026, nearly all DNS traffic still travels unencrypted over your ISP’s network, where it gets packaged and sold to programmatic ad exchanges. DoH, DoT, and the new DoH3 protocol make that surveillance technically impossible.
