Live data from Hacker News

A guide to set up your own round-robin DNS-over-HTTPS proxy for privacy

dohproxy.com

11–20 of 47 posts

Re: A guide to set up your own round-robin DNS-over-HTTPS proxy for privacy

#11

A quick bug report: you do not need to set up renewals in cron. In the certbot ppa (and Debian, and thus Ubuntu), they're automatically set up for you at the time of install using both cron and systemd timers.

Noted, and thank you for the PR! The instructions have been updated

Re: A guide to set up your own round-robin DNS-over-HTTPS proxy for privacy

#12
post #10

Earlier quoted context omitted.

Indeed, that and SNI[1] make this whole DoH thing pretty pointless for privacy IMHO --- if you are seriously concerned about your ISP monitoring your traffic, tunnel everything through a VPN that exits into the Internet somewhere else. It seems more like an effort to frustrate host-based adblocking more than anything. [1] Looking at SNI is even more accurate, since DNS lookups don't necessarily (but often) mean a con…

Encrypted SNI exists. https://blog.cloudflare.com/encrypted-sni/ I doubt DoH is a ploy to break adblocking; if you don’t control the device making the requests they could already do plenty of things to break crude adblocking techniques like that. (Nevermind the fact that one of its biggest supporters is Mozilla.) Stating that this is pointless for privacy seems like an exaggeration. Sure its not a panacea, but for pr…

Exactly; this isn't suitable for people evading nation-states but I use it for my home network as another layer in privacy where total traffic proxying or all-over-Tor isn't realistic.

Re: A guide to set up your own round-robin DNS-over-HTTPS proxy for privacy

#13
post #3

I thought this was someone else providing an anonymized dns proxy at first, but it's just how to set up your own proxy. Not sure this saves anything over just using DoH to one of the listed providers directly (the requests still come from something you own and can technically be traced back to you, albeit with more effort?) edit: I'm wondering what the ideal setup actually is. Would the root servers need to provide D…

The "more effort" part was what I was going for -- no nation state or warrant-holding organization is going to be stymied by this, but as a personal/home user, I'd rather DoH resolvers not be able to tie my lookups to my personal IP which is doubtless held in many other cross-referencable locations (in my case, home-network wide proxying or Tor isn't feasible).

I wonder if it'd be feasible to proxy only the DNS requests over Tor. Maybe set up your network-level DNS proxy to route upstream queries through a Tor tunnel to a different DNS-over-HTTPS resolver. Perhaps even have the DNS proxy cache DNS records and proactively revalidate commonly used ones to avoid most of the latency overhead of Tor.

Re: A guide to set up your own round-robin DNS-over-HTTPS proxy for privacy

#14
post #5

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, su…

You only get privacy from Cloudflare 3/4 of the time, as their resolver is one of the four requests are proxied to.

But 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

Re: A guide to set up your own round-robin DNS-over-HTTPS proxy for privacy

#16
I think if you go for privacy it is best to resolve queries recursively. You can do QNAME minimization with unbound for example and whatever network you are trying to reach will likely see your address anyways some way or another. I mean i for one am more worried about a centralized service like offered by cloudflare then i am worried that individual nameservers tracking me. And if you are worried about people being able to sniff on your traffic protecting only dns from that wont help you much.

Re: A guide to set up your own round-robin DNS-over-HTTPS proxy for privacy

#17
post #3

I thought this was someone else providing an anonymized dns proxy at first, but it's just how to set up your own proxy. Not sure this saves anything over just using DoH to one of the listed providers directly (the requests still come from something you own and can technically be traced back to you, albeit with more effort?) edit: I'm wondering what the ideal setup actually is. Would the root servers need to provide D…

In my opinion it would be ideal if all namerservers (including the root servers) would respond to DNS over TLS (DoT?) traffic which seems like it could be easily adopted but would probably increase the load considerably in some cases (i guess root servers see some massive amount of traffic)... i dont think this will happen anytime soon with DoH or DNS over TLS

Re: A guide to set up your own round-robin DNS-over-HTTPS proxy for privacy

#18
post #5

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, su…

You only get privacy from Cloudflare 3/4 of the time, as their resolver is one of the four requests are proxied to.

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.

Re: A guide to set up your own round-robin DNS-over-HTTPS proxy for privacy

#19
post #13

Earlier quoted context omitted.

The "more effort" part was what I was going for -- no nation state or warrant-holding organization is going to be stymied by this, but as a personal/home user, I'd rather DoH resolvers not be able to tie my lookups to my personal IP which is doubtless held in many other cross-referencable locations (in my case, home-network wide proxying or Tor isn't feasible).

I wonder if it'd be feasible to proxy only the DNS requests over Tor. Maybe set up your network-level DNS proxy to route upstream queries through a Tor tunnel to a different DNS-over-HTTPS resolver. Perhaps even have the DNS proxy cache DNS records and proactively revalidate commonly used ones to avoid most of the latency overhead of Tor.

Unbound does prefetch [0]. Not sure abt the tor split tunnel, but is easy to setup one over WireGuard.

[0] https://en.m.wikipedia.org/wiki/Unbound_(DNS_server)#Feature...

Re: A guide to set up your own round-robin DNS-over-HTTPS proxy for privacy

#20
post #10

Earlier quoted context omitted.

Indeed, that and SNI[1] make this whole DoH thing pretty pointless for privacy IMHO --- if you are seriously concerned about your ISP monitoring your traffic, tunnel everything through a VPN that exits into the Internet somewhere else. It seems more like an effort to frustrate host-based adblocking more than anything. [1] Looking at SNI is even more accurate, since DNS lookups don't necessarily (but often) mean a con…

Encrypted SNI exists. https://blog.cloudflare.com/encrypted-sni/ I doubt DoH is a ploy to break adblocking; if you don’t control the device making the requests they could already do plenty of things to break crude adblocking techniques like that. (Nevermind the fact that one of its biggest supporters is Mozilla.) Stating that this is pointless for privacy seems like an exaggeration. Sure its not a panacea, but for pr…

Yep. Encrypted SNI is still a work-in-progress in terms of browser support – like DoH itself – but they’re both being pushed by Cloudflare, and intended to complement each other. No conspiracy theory needed to explain the motivation.

Edit: And Cloudflare‘s own service mitigates the use of IP addresses to identify sites, since (AFAIK) all Cloudflare-wrapped sites are accessed via the same IP. Of course, this is only an improvement if you trust Cloudflare.

Post reply on HN