The keys to the Internet change on October 11, 2026. Are you ready?

Open original

The Internet's DNS system is replacing its root key-signing key for only the second time on October 11, 2026. Most sites need no action, but validating resolvers must trust the new key beforehand or websites could become unreachable for their users.

  • KSK-2024 (key tag 38696) will replace KSK-2017 as the signer of the root's DNSKEY set. Resolvers that don't trust the new key before the switch could make all websites unreachable under any top-level domain for their users.
  • The new key has been published since January 2025 to give resolvers time to discover it automatically via RFC 5011, but Cloudflare added it to their resolver software's built-in trust anchors in July 2024 after learning from 2018 rollover failures where upgrades and machine moves caused resolvers to lose learned keys.
  • RFC 8509 now lets you test whether your resolver trusts KSK-2024 using a readiness test tool that queries sentinel domains—this capability didn't exist for the 2018 rollover.
  • The rollover continues into 2027 when ICANN plans to revoke KSK-2017 and delete its private key. A future algorithm change to ECDSA is planned separately.

On October 11, 2026, the DNS root will swap out its key-signing key (KSK) for only the second time in history. This key anchors DNSSEC, the system that lets DNS resolvers verify website addresses are authentic through cryptographic signatures. The new key, called KSK-2024, replaces KSK-2017. The stakes are high: if resolvers don't trust the new key before the switch happens, users could lose access to websites across every top-level domain, even though the sites themselves are working fine. Most website operators don't need to do anything. If you run your own DNSSEC-validating resolver, you need to make sure it trusts KSK-2024. Cloudflare's 1.1.1.1 resolver and similar services already have it built in. DNSSEC works as a chain of trust flowing from the root down through top-level domains to individual websites. Each level publishes digital signatures that the resolver checks using public keys from the level above it. The root is different—it has no parent to vouch for its keys, so resolvers start with a trust anchor, a root public key they already know to trust. The root actually uses two keys: a zone-signing key that signs DNS records, and a key-signing key that signs the list of public keys itself. KSK-2024 has been published alongside the old key since January 2025, giving resolvers time to discover and accept it through automatic updates. Cloudflare added it directly to their resolver software in July 2024 to avoid the problems they saw in 2018, when some resolvers lost track of the new key during software upgrades or when moving between machines. To check whether your resolver is ready, Cloudflare built a readiness test using RFC 8509, a standard that lets you query a resolver to ask if it trusts a specific root key. The test works by sending two specially crafted DNS queries: one asking "is this key trusted?" and another asking "is it not trusted?" A resolver that supports the protocol will return different answers depending on whether it actually trusts KSK-2024. You can run the test yourself using the `dig` command against 1.1.1.1. The test also includes controls to rule out false results from failed lookups or resolvers that don't support the protocol yet.

Ask about this article