3 ms·
> DNS interference is being mitigated by the CA system Such mitigations (e.g. 0x20 or multi-perspective) are not enough to outrun the metaphorical bear. So the
by tialaramex 7y ago
> DNS interference is being mitigated by the CA system
Such mitigations (e.g. 0x20 or multi-perspective) are not enough to outrun the metaphorical bear. So they only work until you are slowest again. Putting such mitigations in place for those who can't or more often won't deploy DNSSEC makes sense, but somebody will get eaten by the bear this way.
> unlike other security controls, DNSSEC fails by dropping the site off the internet
You could do some small UX work here to have an explicit error like the ones for TLS version interference, but it's of dubious value. Also you're probably thinking this is valuable feedback to site owners but unfortunately it'll be choked with noise. TLS version interference, for example, mostly means your crappy anti-virus or other middlebox garbage is causing problems. But it might be an attack, or a dodgy cable... who knows. As with certificate expiry the right thing for a site owner to do is have their own alerting in place.