2 ms·
> At this point we should choose our own recursive DNS provider Assuming you control your device (non-corporate non-government users) and know how to configure
by peterwwillis 11y ago
> At this point we should choose our own recursive DNS provider
Assuming you control your device (non-corporate non-government users) and know how to configure your DNS server (elite users only) and wanted to do this extra step (privacy-conscious people?), this will break for hotels, airports, cafes/restaurants, corporate/government networks, anyone with an ISP that intercepts public DNS requests, and various home routers. Not to mention making surfing the web much slower and less reliable, since we distribute name servers specifically to rely on caching to lower latency and increase availability in case of various network failures.
But otherwise, sure, that works.
- jessaustin 11y agoAssuming you control your device... If this isn't the case, then I know that the device operates not in my interest, but in that of whoever controls it. So, I probably won't be entering any sensitive information into it.
- peterwwillis 11y agoLike your work e-mail?
- jessaustin 11y agoEmail is rarely a good place for sensitive information. DNSSEC is not a panacea, but it does make Eve's job harder. https://insights.sei.cmu.edu/cert/2014/09/-probable-cache-poisoning-of-mail-handling-domains.html https://insights.sei.cmu.edu/cert/2014/09/-probable-cache-po...