• Sources: primary, IANA ceremony schedule, discussion
  • Summary: On 2026-10-11 the DNS root switches the signer of its DNSKEY set from KSK-2017, key tag 20326, to KSK-2024, key tag 38696, which is only the second root KSK rollover ever, and both keys use RSA/SHA-256 so the key pair changes without an algorithm change. KSK-2024 has been published in the root DNSKEY set since 2025-01-11 so RFC 5011 automatic updates have had time to accept it, and Cloudflare reports that resolvers nonetheless lost learned anchor state during software upgrades and machine moves ahead of the 2018 rollover, which is why it added the key to its resolver's built-in anchors in July 2024 rather than relying on learning. Cloudflare has implemented the RFC 8509 trust anchor sentinel in 1.1.1.1, so a resolver can be asked directly whether it trusts key tag 38696 through is-ta-38696 and not-ta-38696 queries under a signed domain.
  • Why it matters: A validating resolver that does not hold the new trust anchor can fail to resolve names under every top-level domain, and the failure mode is a working site that is unreachable rather than an error that points at DNS, so operators of self-run validating resolvers need to confirm the anchor is present and follow their vendor's trust-anchor update instructions, while users of Cloudflare DNS, 1.1.1.1 and Gateway DNS and most website operators need no action.
  • Follow-up: The 2026-10-11 switch date rests on Cloudflare's post, and IANA's ceremony schedule corroborates only that KSK-2024 was generated on 2024-04-26 and imported on 2024-07-17 and that KSK-2017 is set for deletion at a ceremony on 2027-04-29, so watch for an IANA statement that makes the date primary and for resolver failure reports after the switch.