2 ms·
But that's the thing, common server software already collapses that part of the protocol into a single operation for the query itself. To enable DNSSEC for most
by jeroenhd 5y ago
But that's the thing, common server software already collapses that part of the protocol into a single operation for the query itself. To enable DNSSEC for most systems, you just tell your nameserver to sign the zone and copy the necessary keys over to your registrar. That's two commands in PowerDNS, one to sign the records and one to fetch the keys. In BIND it requires some manual key generation and config, but that's still hardly a challenge for someone who can manage their own DNS zones. CDS/CDNSKEY can automate the communication with the TLD provider, but that's completely optional.
The real jankiness is hidden away in the bespoke implementations on the backend that are designed to have their own complex DNS logic. Those systems don't need to abide by the weird offline-signing DNSSEC standards at all, because there's no reason for them to be compatible with other servers unless you're glueing your own code to an existing server. The offline signing quirk also actually helps you if you use a master/slave DNS setup because you don't need to set up a complicated multi-keyed DNS system to have many resolvers serve your records; one place signs it, and the other servers just forward the responses.
The client does nothing more complex than validating the chain of trust like we're already doing for every other part of our modern connections, and all the server needs to do is respond with the right records (be it signed responses or signed errors).