Blocky – a DNS proxy and ad-blocker for the local network
0xerr0r.github.io
0xerr0r.github.io
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 that if you make DNS resolution distributed across providers, you might be exposing your "trail" to multiple companies at the same time, compared to an alternative approach of switching every X minutes so that any individual company only sees a snapshot of your queries in time rather than your whole journey.
> For spreading DNS providers, would randomly routing to different ones be more or less private than rotating providers every X minutes.
Less private for the simple fact that now you'd have to rely on multiple upstream resolvers to respect your privacy. Stick to one; ideally the one with better privacy guarantees like the Mozilla endpoints to Cloudflare DNS.
Or, use anonymizing protocols like Oblivious DNS over HTTP and DNSCrypt v3.
If privacy is what you're intending however, DNS is only one part of that and there are other ways in which things can leak https://www.privacyguides.org/en/advanced/dns-overview/
Generally I just recommend to people to use their internal VPN provider's DNS servers and call it a day, or of course Tor.
My ISP can already see where I go and what I do anyway.
But you do you, friend.
Oh, I did not know that Mozilla had an endpoint on Cloudflare's 1.1.1.1 service, but there it is!
https://github.com/mozilla/gecko-dev/blob/c09764753ea40725eb...
https://mozilla.cloudflare-dns.com/dns-query
Does Mozilla publish their terms somewhere? I'm curious how their endpoint is any different.
More info on why Tor chooses just a few entry nodes here: https://support.torproject.org/about/entry-guards/
Is that the consensus? I thought this would just increase the amount of parties that have insight. eg if today it sends my CNN news reading to cloudflare and tomorrow it sends it to 9999 resolver then that seems worse than sending both to cloudflare.
Or NextDNS to let someone else handle it.
Blocky is better because it uses less resources ,only a single yml onfig file and dns queries are faster as it's stateless
If you report a website breaking to the maintainer, he removes the offending block.
Works well, I can recommend it.
And it reminds my to send them a little money in thanks.
Such problems are few and far between, though, and it wasn't that hard to figure out what to whitelist (granted I'm a computer nerd, not everyone is).
Now every time, I have an issue with any website, my first instinct is to turn off pi-hole. Most of the time, pi-hole is not the even the issue, but sometimes it is. It's annoying to browse the internet while constantly thinking "Maybe there is an issue on my side".
It is very rare that I find something stalker-blocking (pihole on my local network & VPN) causes to break that I care enough to turn blocking off for. It might have happened as little as twice, one of those occurrences predating PiHole. Information is usually in many other places or I really don't care that much, and shopping sites that break are waving a red flag by being broken so I'll go look elsewhere.
I do have a bookmarklet on my devices to turn it off for a few minutes, but that was used more when testing it then it has been since.
I mostly live alone so don't have the problem of other users, such as a spouse or kids, having trouble. Guests always have the option of using their normal mobile access instead of the local wireless if they experience insurmountable problems.
I'm typing this response not to smugly boast, but because it's a lead in to the question that your comment raised within me:
Are you using Pihole to block ads at a network level, but not also using a browser extension to block them at the client?
So in my case, I don't know that an ad blocker really even helps me on google, because I'm ignoring those first results anyway.
A lot of Pihole users don't bother with browser extensions. In extension-only use cases, these results would just not show up. With Pihole, you have to copy and paste the URL and just enter directly in the browser. It's not like a huge roadblock.
or simply these URLs:
Disable URL : http://<pihole ip address or hostname>/admin/api.php?disable&auth=[your pihole password]
Enable URL : http://<pihole ip address or hostname>/admin/api.php?enable&auth=[your pihole password]
Disable for [X] Seconds: http://<pihole ip address or hostname>/admin/api.php?disable=[X]&auth=[your pihole password]
So for example, if you make a container with this, then you can just quickly open the URL that's blocked in the other container and it will bypass the network-level DNS adblock.
There are other ways to do it without a container, I'm sure, maybe with an add-on/toggle or something.
My VPN provider gives free SOCKS5 access to a few servers, so it didn't cost me anything more.
Bookmark it for myself and other people in the house and then turn it off for five mins whenever there is an issue.
In adguard home you have a switch on/off in the web UI. You can also expose that switch to homeassistant.
And there are some other good ideas in this thread as well for android and ios.
It’s easy enough to just connect to a different ssid if I see anything breaking, but it’s rare enough that I keep it connected to the pihole/adblock network at all times. Works super well.
They’re mated to a Juniper EX switch running stock JunOS over PoE, primarily one AP for each floor and another one or two to fill in dead spots. I haven’t had to touch it since I’ve set it up, just keeps chugging along.
Slight over-kill for the environment, but I’m so damn tired of using bad wifi I just wanted to do it right!
Most issues were with Google Ads inside Google Search. Often these are relevant and actually what you're looking for. But they don't work.
I tried rewriting the "this is blocked" page that PiHole would serve so it included a button to temporarily disable blocking for said url but it turned out to be harder than I thought.
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 download apps that do the same thing; I have one called "Pi-Hole Remote" that works great.
Yes, ad blocker blockers are annoying, but they are trivially worked around.
https://apps.apple.com/nl/app/pi-hole-remote/id1515445551?l=...
Any hints?
And then it's back to doom scrolling
https://github.com/yattee/yattee
it requires either public or private Piped or Invidious instaces [1][2].
Edit: forgot to add link - https://revanced.app/
Be aware of the fake ones.
You'll need to generate your own CA and root certs to install if you're setting up a MITM proxy.
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
So blocky can block IP addresses? If so it's more powerful than traditional DNS blockers like Pi-Hole and AdGuard Home.
> Logging of DNS queries per day / per client in CSV format or MySQL/MariaDB/PostgreSQL database
May want to include a time series database, like InfluxDB
For those needing layer 7 control, https://github.com/andybalholm/redwood is a nice Go option.
Seems to have native support for Prometheus, so that seems to be the TSDB to use for the project. That said, if you're at the point where your record density takes advantage of the benefits of a time series DB vs a well indexed RDBMS, I'd also imagine that you're beyond the scope of this little service.
https://github.com/AdguardTeam/AdGuardHome/discussions/4002#...
conditional:
mapping:
archive.is: 8.8.8.8
archive.today: 8.8.8.8
archive.md: 8.8.8.8
archive.ph: 8.8.8.8 server=/archive.today/8.8.8.8
server=/archive.ph/8.8.8.8
server=/archive.is/8.8.8.8
server=/archive.li/8.8.8.8
server=/archive.vn/8.8.8.8
server=/archive.fo/8.8.8.8
server=/archive.md/8.8.8.8
server=/archive.to/8.8.8.8I have simply set https://dnsforge.de in my router.