3 ms·
The privacy noted here appears to essentially boil down to “from Cloudflare” right now, and comes at the risk of leaking DNS queries to other third-parties who
by floatingatoll 7y ago
The privacy noted here appears to essentially boil down to “from Cloudflare” right now, and comes at the risk of leaking DNS queries to other third-parties who are often more inclined to act maliciously towards your privacy and are not committed against doing so.
Be sure that you trust your “over the wire” connection to not sniff and uniquely tag all of your DNS requests with your specific identifying information, such as Verizon and many other service provides often do.
- goatsi 7y agoYou only get privacy from Cloudflare 3/4 of the time, as their resolver is one of the four requests are proxied to.
- jkingsman 7y agoThe idea is that resolvers just know it's coming from the EC2 instance/etc rather than knowing your personal IP.
- gog 7y agoThey know the personal IP as well since it's being passed in the "X-Forwarded-For" header by nginx. Having a local recursive resolver with the Client Subnet in DNS Queries turned off would be better for privacy.
- kardos 7y agoBut it's round robin. So give it a bit more time and they get a pretty complete picture. Eg if you resolve neopets.com every morning, they just need to wait (approx) 4 days to capture the request
- ignoramous 7y agohttps://simplednscrypt.org https://simplednscrypt.org for Windows has a one-click setting to enable round-robin over 20+ DoH, DoT, DnsCrypt servers. I don't see why anyone must use a proxy for DNS only to incur additional latency.