2 ms·
Unfortunately, because all domains don't yet have DNSSEC DNS records, a strict resolver that requires DNSSEC signatures will fall to resolve all domains unless
by westurner 5y ago
Unfortunately, because all domains don't yet have DNSSEC DNS records, a strict resolver that requires DNSSEC signatures will fall to resolve all domains unless it's configured to e.g. "allow-downgrade" to non-DNSSEC-signed records for any lookup.
FWIR, the same is basically true of DoH and DoT: if it's not configured to ~allow-downgrade, DNS will fall to resolve when connected to e.g. a captive portal hotspot; and there's no indication that DoH/DoT aren't working in the browser.
How do DNS resolution APIs need to change to accommodate basic DNSSEC and DoH/DoT error handling?
- tptacek 5y agoDoH and DoT don't have the same failure modes as DNSSEC --- a TLS failure during a DoH lookup is much more likely to actually be the result of a break in the chain of trust than a DNSSEC failure is.
- westurner 5y agoWhat fields are there in the error structs? FWIU, Status quo: In browsers we have: - a broken lock icon, a cert failure error page for manual error resolution, and a cert information dialog