Also using this on the go through VPN
Also using this on the go through VPN
Same. Wireguard is a beautiful thing.
Which VPN service? I normally use Tailscale with the Pi as an exit node, but I'd like to have simultaneous VPN connection
I think people just use wireguard for this. And pivpn.
Same here. Wireguard.
Out of the box, pihole has a few block lists already set up. Those are pretty good already.
To add more, you can find some good block list collections online. No need to add them all. Pick a good handful, depending on the category of stuff you want to block. Here are some helpful links:
https://github.com/lightswitch05/hosts
... Once you got a few block lists set up, you'll probably want to whitelist some things specifically, that are otherwise caught up in the filter. This is a super helpful resource for that:
There's a script on github (don't have the link right now) for an automated whitelist. I was expecting it to break some things or end up useless, but it was the perfect addition for me Edit: https://github.com/anudeepND/whitelist
Yup. Another piHole user.
Adguard Home. I find it to be more feature complete, compared to Pi-Hole. Nicer GUI, more options, built in DNS-over-HTTPS/TLS, better client controls & detection, more domain information, better domain list blocking, and so on.
I moved from NextDNS, to Adguard Home. All self hosted, and accessed with a reverse proxy.
Same, used NextDNS and Pi-Hole then move to AdGuard Home til today.
Built-in (DoH, DoT,...) servers are useful and simple to setup with client identification.
Are you guys not concerned about losing complete access to the internet if something drops on your server?
I realise these will be very rare cases, but shit happens sometimes, and always seems to happen at the worst possible moments.
What's your recovery plan?
Edit to add that this is the reason I'm on nextdns... Make it someone else's problem
You do have two DNS options on most devices. A Primary and a Secondary. If you're worried about your primary's stability/reliability, put a different dns as your secondary that you trust.
It's not hard to setup a pi as a backup DNS on your local network,, but how I've setup a few friends who have limited hardware is to have the primary DNS as the local adguard and the secondary DNS as adguards public adblock DNS
That way if the local falls over, you still get some as ad blocking from their public one. If your setup allows it, they also have a public doh and dot encrypted dns for a bit of privacy
I was able to test it out first without having to create an account and I liked it. It has simple Ad/Tracking blocklists and supports both DoT and DoH. Also it has rewrites (like /etc/hosts).
For me, Nextdns. It's mostly because I can choose which list is used by the dns blocking. If adguard has a lost blocking what I use, I can't do anything about it. Or maybe like allow a lot of domains.
Using the Hagezi pro++ list currently and it works damn well without any issues for me.
Also, there is a free way to use it (not sure about adguard).
Adguard home for everything
nextdns is the most performant option I've used. it often beats our cloudflare even. adguard wasn't bad but it was a bit more cumbersome and very slow.
I don't like recommending self hosting as opening ports on a private network isn't a great idea. you could use something like cloudflare or tailscale to bridge access but you'll run into issues with network speeds.
most people don't nor do the aforementioned measures have substantial documentation that is easily accessible by the average user.
they aren't even meant for enthusiasts but rather, in industry professionals
enthusiasts become industry professionals.
And if substantial documentation were the only thing that kept networks from security and absolute anarchy, then all of the internet would be lost.
It's not documentation, nor is it absolute knowledge that brings someone to understand a sane amount of security. But also trial and error.
One of the most important first rules of security is, start testing in applications that pose the least amount of risk.
If you're looking into hosting your own DNS server, you've already proven you understand a lot more than the average user does about networking in general.
I just use ublock origin
Pi-hole for my home network. NextDNS on my phone.
Sure! If you've got that pi on all the time. I previously did that and it worked well. My current setup is multiple pi's though, cause the octo pi is switched off with the printer now..
I had it setup using docker at the time. Both pihole and octoprint as individual containers...
But I assume you should be able to just install and run the package locally on the octopi distro.
Adguard home with a few extra lists and custom rules. Just got the sync tool set up to auto replicate changes from one to another so no more copy/paste to a secondary. Great when I need to restart a VM and don't want to take out the internet while it reboots.
Used pihole some while back but the feature list was tiny by comparison, though it was a good while back so probably unfair to compare.
Also ran with pfBlocker for a while, nice to have it right on the gateway but found it a bit opaque and lacking customization for my needs.
NextDNS. Several years now. It’s absolutely brilliant.
mullvad!
does quad9 block ads as well? I thought it was only trackers
Blocky installed locally as a service for my PC https://github.com/0xERR0R/blocky
RethinkDNS for my phone https://rethinkdns.com/configure
Controld.com
PiHole with the Star Trek web UI theme. I think it looks pretty nice and has worked well for me.
I use Adguard because it's pretty reliable and solid.
I would love other options but I haven't found many that rival Adguard. I'm very picky about DNS because frequently services that I use can detect them and most free providers do nothing to alleviate blocking.
I use two across different devices.
base.dns.mullvad.net
noads.libredns.gr
Both offer DNS over TLS and both are privacy focused which was why I decided to use them.
Does DNS over TLS have any advantages over DNS over HTTPS?
Not really and some would argue that from a local network perspective HTTPS is preferable.
The main difference is that HTTPS routes through a standard port so gets "lost" in all other Https traffic whereas TLS uses a distinct port so whilst it's encrypted you would be able to see at the local level that you're using DNS over TLS but not what you're doing.
Thanks for the explanation. Doubt I would have found such a simple answer if I went searching.
Adguard Home on the homelab, with my router set to use it as DNS, alongside Tailscale with Headscale on top to reroute all traffic through the home network so that ad blocking works all the time, on all devices that can use Tailscale, and also away from home.
im using cloudflare doh as upstream. and setting my own dns server (dnsmasq) with ad block hosts on my router
Blokada 5 .... local blocklist > cloud VPN
Control D
thanks for using Leebra!
go to feed...
Pi Hole with a few good block lists...
save