5 ms·
I absolutely love the DNS based solution for ad-blocking and preventing tracking. I use AdGuard DNS on my PC (DNSCrypt) [0] and phone (DoTLS) [1], and it has im
by ignoramous 8y ago
I absolutely love the DNS based solution for ad-blocking and preventing tracking. I use AdGuard DNS on my PC (DNSCrypt) [0] and phone (DoTLS) [1], and it has improved performance of apps (not just websites), 'cause I guess there's a lot less going on under the hood now (trackers like new-relic and segment might be consuming a good percentage of resources which they wouldn't now since their domains are NX'ing?).
What am I worried about is DNS based black-holing is trivial to workaround against (as an ad-provider, one could simply force use a custom DNS client and pin to a DNS resolver of choice) [2][3][4]. What's next for pi-hole and solutions like AdGuard DNS short of re-writing packets going through UDP/53? Not sure how one would intercept the DoTLS / DoHTTPS connections, to rewrite those.
I'd like to hear if anyone has some thoughts on this, or if this has been discussed elsewhere.
[0] https://simplednscrypt.org/ https://simplednscrypt.org/
[1] https://news.ycombinator.com/item?id=18788410 https://news.ycombinator.com/item?id=18788410
[2] https://news.ycombinator.com/item?id=19170671 https://news.ycombinator.com/item?id=19170671
[3] https://news.ycombinator.com/item?id=19106023 https://news.ycombinator.com/item?id=19106023
[4] Firefox 64 for PC, by default, was configured to ignore OS/Network Interface provided DNS resolver and used CloudFlare's over HTTPS.
- wnissen 8y agoI bought the Pi-Hole kit for ~$US100 but was never able to get it to work properly with SSL/TLS sites despite some (admittedly cursory) Googling. It's a great idea in theory. https://uk.pi-supply.com/products/pi-hole-kit-network-wide-ad-blocker https://uk.pi-supply.com/products/pi-hole-kit-network-wide-a...
- vultour 8y agoIs that a raspberry pi and some cables sold for $100?
- the_jeremy 8y agoNo, there's also a 16GB SD card with the software preloaded, and a plastic cover. Basically.
- homerhomer 8y agoSomebody is overcharging you on this one. I installed it on my Raspberry Pi B from like 2012. I installed Raspbian, input a small one liner and it was installed.
- wnissen 8y agoWAIT, just updated to the latest version and it's working great now. All I had to do was set my Airport to use the Pi-Hole for DNS and now every device on my home network is 99% ad-free. Very impressive.
- zamadatix 8y agoDoTLS and DoHTTPS can be intercepted on your own devices by adding a privately generated certificate to your root store and MITMing the traffic. By design this is the only way to filter this traffic based on content. Regardless name resolution based ad blocking is relatively futile against even naive workarounds. For instance what is to stop someone from using a custom DoHTTPS format on any webpage to resolve the name directly in browser? What's to prevent them from obfuscating it in a way your MITM couldn't realistically detect? In the end ad blocking is best done directly on the client through something like uBlock Origin. Not only does this allow you to create a network request block list (now with the added capability of reading/filtering on the whole URI) but it also allows for style based blocks where the ad content could even be blocked if it comes from the same server and resources serving the actual page.
- inapis 8y agoYou honestly need both. Of course, a pihole will not be able to block someone who goes to the length of developing and using a custom DNS-over-TLS or DNS-over-HTTPS webpage. Similarly uBlock origin is not available for anything else except browsers. There is nothing preventing native apps from using or pinning different nameservers. On a scale of hardness, using or pinning a specific DNS server is easy and is known to be used in wild. Custom DoT or DoH is still rare but I am aware that there will be a time when a significant chunk of internet will use it. Name-resolution based ad-blocking is not futile yet. My pihole has alone blocked 5k+ queries in the past 24h.
- foxes 8y agoWhat native apps are you running have advertising built in? That sounds horrifying.
- JonAtkinson 8y agoWindows 10?
- Haga 8y ago
- sudo-i 8y agoI have a pfsense box. It's quite arbitrary to block DNS request that are anywhere except to your pfsense box. eg. https://docs.netgate.com/pfsense/en/latest/dns/blocking-dns-queries-to-external-resolvers.html https://docs.netgate.com/pfsense/en/latest/dns/blocking-dns-...
- 1over137 8y agoIf I'm not mistaken, that will work only for regular old DNS, not DNS over HTTPS (DoH), which, I presume, uses port 443, not 53. Seems like blocking Firefox and Chrome from usurping your DNS choices is going to be much harder going forward. :(
- stephen_g 8y agoIt’s going to have to work though. For example, corporate users absolutely require the ability to access private internal domains that are not served by public DNS servers. The browser vendors aren’t going to be able to enable DoH directly from the browser by default and break that. I think the main reason the browsers have added support is so they can get the data they need to make encrypted SNI work. They’re going to have to get operating system APIs to be able to do this from the OS’s resolver or else it will screw all sorts of things up.
- sudo-i 8y agoTLS it seems it actually uses port 853 (which I didn't know). https://tools.ietf.org/html/rfc7858 https://tools.ietf.org/html/rfc7858 So I guess in theory you can block that port outbound to all hosts to handle TLS's use case. HTTPS is tougher, but just block all traffic to those hostnames with a DNS blacklist.
- jlgaddis 8y agoThat's DNS-over-TLS which, while similar, is something completely different than DNS-over-HTTPS (DoH). DoH does, in fact, use 443/TCP, just like regular HTTPS traffic.
- 1over137 8y agoRe #4: really?! I missed that news. Sounds horrible. So instead of using my ISP, that I chose and trust, all my DNS queries now go to some foreign megacorp?!
- meowface 8y agoThis is also the first time I heard about it, but my immediate reaction was "sounds amazing". - Removes all DNS leak privacy issues, for all Firefox users, automatically - Removes all possibility for a MitM to view or corrupt DNS queries or responses, for all Firefox users, automatically And Cloudflare claims to delete all DNS-related logs of Firefox users within 24 hours: https://developers.cloudflare.com/1.1.1.1/commitment-to-privacy/privacy-policy/firefox/ https://developers.cloudflare.com/1.1.1.1/commitment-to-priv... Even if you distrust Cloudflare or think they're not secure against breaches, it's still a massive security and privacy upgrade over using your ISP's DNS servers, which will pretty much always leak sensitive information about your connection (potentially leading to deanonymization while using an anonymizing service) and send/receive everything in unauthenticated plaintext. And in addition, your ISP likely is less trustworthy and less secure against breaches (even if you aren't using Comcast, Verizon, or AT&T) than Cloudflare. But again, even if you don't trust them, this would still be the best move for security. Plus it's a big latency decrease and performance boost for most or all users.
- kllrnohj 8y agoWho said the router on the network I'm connected to handed out a DNS server that was from my ISP? And why are you so sure my ISP is less secure & trustworthy than Cloudflare?
- kasey_junk 8y agoAt least in the US nearly all ISP are either directly selling their customer data or own outright publishing arms that rely on advertiser revenue. Even in Europe big telcos like Telenor have adtech holdings. It doesn’t mean you can’t trust your ISP but certainly there are red flags.
- 3xblah 8y agoLike Vixie said, route and answer 8.8.8.8. He is complaining that he has to do it. He is not saying that there is no solution. Putting a DNS client in Chrome (I think they removed it but who knows), or Chromecast, or whatever is "evolutionary pressure". It forces users to evolve the solution to work around it. This is good. If users are forced to learn to use an RPi for DNS (and we can see they are doing that with Pi-Hole), and eventually another pocket-sized computer with open-source software for routing, that benefits the community of users who want to avoid ads. If avoiding ads is the goal, then using a pocket-sized computer with a user-installed OS is better than a solution marketed by a commercial third-party, as almost always those third parties rely partially/wholly/directly/indirectly on the ad business.
- muppetman 8y agoI don't understand Vixie. I have a Chromecast Ultra. On my Firewall at all, I reject all requests to 8.8.8.8(and .4.4) with a ICMP unreachable. This forces the CC Ultra to use the DHCP allocated DNS Server (a pihole) which works just fine. I don't understand why he says you have to route and answer 8.8.8.8. You really don't. If his point is you can't override the built in DNS without some sort of FW hackery though, then yea his point stands.
- 3xblah 8y agoDoes the dest unreach solution work on the original Chromecast?
- _emacsomancer_ 8y agoWhat is "Firefox 64 for PC"? Does this mean non-mobile Firefox?
- caioau 8y agoI have an openwrt router and also use a DNS adblocking, but there's a iptable rule that forces the clients using the router's DNS
- toredash 8y agoCould just point to an IP directly as well. That could be blacklisted as well but in today's tech stack it is really easy to change variables so that a block would have a short term effect on the client.