Anecdotally, NSEC3 was known at its inception to be insufficient but done anyway to hush privacy advocates.
9 karma · joined June 1, 2023
Anecdotally, NSEC3 was known at its inception to be insufficient but done anyway to hush privacy advocates.
Clients absolutely do get RRSIGs (and relevant NSEC/NSEC3) however they don't necessarily validate them.
That really only works well for web servers. If your service isn't the one found at the A/AAAA lookup for a given name it's much more difficult to obtain a cert for that name, and without that clients are reliant on what's in DNS alone to make the association.
My comment wasn't suggesting a HTTP background is necessary for someone to help move the DNS ecosystem forward.
DNSSEC's lack of maturity is a symptom of DNS itself not having a healthy ecosystem. I feel like it'd take as little as a half-percent of the people writing new HTTP tooling to noticeable improve the DNS ecosystem as a whole.