Cloudflare has extended 1.1.1.1's support to DNSSEC validation using ML-DSA-44, a post-quantum algorithm selected by NIST. The change affects a rarely visible layer of the network, DNS, but addresses an essential component: the ability to verify that a response received for a domain name is authentic and has not been altered in transit.
This update is not equivalent to a widespread conversion of global DNS to post-quantum cryptography. 1.1.1.1 is a public resolver: it receives user requests, queries the DNS infrastructure, and returns the response. With this update, the resolver can also verify DNSSEC signatures built with ML-DSA-44. However, it represents a concrete step toward making a fundamental part of Internet infrastructure compatible with primitives designed to withstand attacks attributed to future quantum computers.
The most instructive aspect of the announcement is the scale of the problem. An ML-DSA-44 signature takes up 2,420 bytes. For DNS, conceived in an era when short messages and compact responses were the norm, this is not merely an implementation detail: it alters the way responses travel across the network and tests intermediate equipment, networks, and software that might not properly handle larger packets.
What DNSSEC protects and why a new signature is needed
DNS translates human-readable names, such as a web address, into the operational addresses and information devices need to connect to services. Precisely because of this role, it is a prime target: anyone able to forge a DNS response can redirect a connection to an unintended destination.
DNSSEC adds an authentication mechanism based on cryptographic signatures. A DNS zone signs its records; the validating resolver checks the signature and the chain of trust leading from the parent zones down to the queried domain. If verification fails, the response should not be considered secure. DNSSEC does not encrypt DNS queries or conceal queried names, but it enables the detection of tampered or inauthentic responses.
The public-key algorithms used by many current systems are built on mathematical problems that a sufficiently powerful quantum computer could tackle much more effectively than conventional computers. ML-DSA-44, on the other hand, belongs to the family of post-quantum digital signatures standardized by NIST. The goal is to offer an alternative path before the eventual availability of quantum machines capable of undermining traditional cryptography turns a complex migration into an emergency.
For DNSSEC, the transition cannot be evaluated solely in terms of algorithmic strength. The signature must be published in DNS records, transmitted by authoritative servers, processed by resolvers, and delivered across a chain of heterogeneous networks. Cryptographic theoretical security must therefore coexist with the real-world limits and behaviors of DNS transport.
The 2,420-byte constraint
The 2,420-byte signature cited by Cloudflare shows why adoption is not straightforward. In DNS, responses can contain not only the requested record, but also additional data useful for verifying its authenticity. If a signature is much larger than those typically used, the entire response grows and can exceed the size that some network paths handle seamlessly.
Over time, EDNS has expanded the protocol's capacity to transport larger UDP responses, while DNS can resort to TCP when UDP is not enough. But actual behavior depends on the compatibility of endpoints and intermediate networks. Filters, firewalls, outdated devices, and misconfigurations can drop or alter unexpected traffic. A response that works in a zone operator's lab could therefore degrade, be truncated, or fail to reach a resolver properly under real-world operating conditions.
For a global service like 1.1.1.1, validating ML-DSA-44 means tackling that variability at scale. Cloudflare thus highlights an issue that will accompany many post-quantum transitions: choosing the algorithm is only part of the work. It requires implementation testing, failure monitoring, and strategies capable of preserving both service reachability and security guarantees.
The risk of fallback is not an operational detail
The other central point concerns downgrading. During a migration period, it is natural to provide compatibility with legacy systems: not all domains will immediately sign with new algorithms, and not all software will be ready to process them. However, a mechanism that automatically falls back to a less secure option when it encounters an error can itself become an attack vector.
An attacker who manages to simulate a compatibility issue could induce a client or resolver to abandon the stronger verification. The result would be paradoxical: the presence of post-quantum support would offer only conditional protection, which could be bypassed by forcing the less secure path. Cloudflare notes that it considered these risks when bringing validation to a global scale, a necessary step in an ecosystem where old and new schemes will coexist for years.
This also explains why adoption will have to be gradual. For DNS zone managers, it is not enough to generate a new key and publish a signature: they must evaluate response sizes, authoritative server compatibility, the resolvers reached, and the consequences of any potential errors. On the resolver side, the challenge lies in properly validating multiple algorithms without weakening the chain of trust under imperfect network conditions.
A signal for the DNS ecosystem
The availability of validation on 1.1.1.1 does not force domain owners to immediately modify their configurations, nor does it immediately change the day-to-day experience of internet users. Its significance lies in making available, within a public resolver used worldwide, a capability that future signers will find already in place. It reduces one of the migration's unknowns: when zones begin using ML-DSA-44, at least a significant portion of the resolution infrastructure will be able to verify their signatures.
The broader work remains ongoing. DNSSEC is not enabled everywhere, and the adoption of post-quantum signatures will require coordinated updates across authoritative software, domain operators, resolvers, and networks. Furthermore, the size of the signatures makes it especially critical to measure what happens outside controlled environments. Any issues will not necessarily be cryptographic: they could emerge in appliances, network policies, or DNS implementations that have assumed smaller responses for years.
The move announced by Cloudflare should therefore be seen as an operational test of maturity, as well as a security update. Post-quantum cryptography enters one of the Internet’s most widespread infrastructures, bringing with it a tangible cost in bytes, compatibility, and exception handling. Addressing it now, before the urgency driven by quantum computing tightens the timeline, is the practical rationale behind the decision made for 1.1.1.1.
