Live data from Hacker News

Blocky – a DNS proxy and ad-blocker for the local network

0xerr0r.github.io

101–110 of 110 posts

Re: Blocky – a DNS proxy and ad-blocker for the local network

#101

Earlier quoted context omitted.

I created a bit.ly link that points to http://yourpiholehost/admin/api.php?disable=300&auth=api_key Bookmark it for myself and other people in the house and then turn it off for five mins whenever there is an issue.

Would be fun to hook this up to one of those IoT Amazon buttons.

Or say “hey google disable ad blocking” and triggering it. Then google learning of this and doing it all the time behind your back

Re: Blocky – a DNS proxy and ad-blocker for the local network

#102
post #67

My problem with network-level adblockers, also PiHole is that they break a lot of services (yeah it's mostly sloppy or malicious intent from service provider but still). On a browser you can quickly disable uBlock for that site, it is much more tedious for these services - also because it's not even clear that the filtering is causing the problem, also because it maybe someone else on the network experiencing the pro…

PiHole has an API that can be used to enable and disable the ad blocker. I have a bunch of home automation set up, and through the use of HomeBridge and a plug-in I have a button in my Apple Home app on my iPhone to enable or disable the ad blocker. Since it's exposed as a smart home thing, you could hook it up to a voice assistant like Siri or Alexa. I built an integration once for an Elgato StreamDeck. You can also…

I’ll definitely implement this as soon as I have the pihole pc back up. My girlfriend will be very happy

Re: Blocky – a DNS proxy and ad-blocker for the local network

#103
post #100
post #68

Why would I use Blocky vs. Pi-Hole? It seems like a nice project but pi-hole is really mature; I'd love to see a feature comparison or a brag sheet showing what it's better at.

I had used Pi-hole and blocky. Pi-hole is nice for the non-expert who just wants to block ads, with a neat web interface. But with blocky, instead of a web interface you can fully configure blocky in a single nice-documented extensive YAML file. Metrics are retrieved per Prometheus and can be visually shown in something like Gragfana. It has A LOT of features and is faster. :)

It looks like it's much easy to setup DoH with blocky. Blocky's DoT doesn't work for me but it's a pain to setup with Pi-hole and it's impossible to make DoH work in Pi-hole.

Re: Blocky – a DNS proxy and ad-blocker for the local network

#104
post #4

> Uses random upstream resolvers from the configuration - increases your privacy through the distribution of your DNS traffic over multiple provider The whole project is really interesting but this line caught my eye. For spreading DNS providers, would randomly routing to different ones be more or less private than rotating providers every X minutes? It feels like so many sites request so many different resources tha…

First thing I thought about was the reasoning behind why Tor uses Entry Guards (a limited set of relays chosen by your client to use as the first entry point rather than a random one each time). I'd imagine the same arguments apply for why you don't want to randomize which servers your DNS queries go to. If you're making hundreds or thousands of queries, as people tend to do while using the same set of sites over time, then eventually all servers will end up with the names of all the sites you visit, as opposed to just choosing one server and only that server having the names. So yeah, that definitely seems like the opposite of a privacy feature.

More info on why Tor chooses just a few entry nodes here: https://support.torproject.org/about/entry-guards/

Re: Blocky – a DNS proxy and ad-blocker for the local network

#105

Earlier quoted context omitted.

I use (and recommend) local recursive resolvers.

It's unencrypted and exposing your IP. From a privacy perspective it's better to use something like Mullvad DNS over DoT or DoH.

Exposing my IP to who exactly?

My ISP can already see where I go and what I do anyway.

But you do you, friend.

Re: Blocky – a DNS proxy and ad-blocker for the local network

#106
post #7

It's a DNS proxy, like pi-hole, but it seems a lot more powerful than Pi-hole that is basically just a configured dnsmasq server to be user-friendly. https://docs.pi-hole.net/

What makes it a lot more powerful? Running pihole just because I know it better than others

Re: Blocky – a DNS proxy and ad-blocker for the local network

#107

Earlier quoted context omitted.

I did create a self signed root cert, it works as expected when accessing net from my Mac. But mobile devices refuse to work, zero network requests succeed. I did trust the root cert on both mac and mobile. ¯\_(ツ)_/¯

Certificate pinning perhaps?

Righto, looks like impossible to fix then.

Re: Blocky – a DNS proxy and ad-blocker for the local network

#108
post #68

Why would I use Blocky vs. Pi-Hole? It seems like a nice project but pi-hole is really mature; I'd love to see a feature comparison or a brag sheet showing what it's better at.

https://youtu.be/UjqZPLL0UvM

Blocky is better because it uses less resources ,only a single yml onfig file and dns queries are faster as it's stateless

Re: Blocky – a DNS proxy and ad-blocker for the local network

#110

Earlier quoted context omitted.

Certificate pinning perhaps?

Righto, looks like impossible to fix then.

On newer versions of android it can be hard to install a root cert and trust it; mitmproxy and httptoolkit both have some great guides though. On iOS its easier - but yeah unfortunately/fortunately certificate pinned applications wont work

Depending on how much time you are willing to put in you could create a list of apps that dont PIN and selectively MiTM apps that dont

Post reply on HN