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
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).
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.
ControlD with AdGuard as backup. Might have to try Mullvad's as well. Then AhaDNS Blitz on my phone.
Can I run pihole on the same Pi that's already running Octoprint?
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.
I roll my own. I created a Docker image that periodically downloads tons of blocklists, smashes them into an Unbound configuration file then runs Unbound with TLS enabled.
On my iPhone and macOS devices I just connect to the encrypted service using
.mobileconfigfiles to apply it system-wide. My home router also uses it as an upstream server (again with TLS) so all connected clients benefit from it as well.im using cloudflare doh as upstream. and setting my own dns server (dnsmasq) with ad block hosts on my router
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.
Blocky installed locally as a service for my PC https://github.com/0xERR0R/blocky
RethinkDNS for my phone https://rethinkdns.com/configure
If you are the "VPN to home, always on" user, go for pi-hole.
Adguardhome has it's strengths when it comes to DoH, DoT, Quic usage.
I use the Adblock plugin on an openwrt router to provide blocklists for the whole lan. It works rather weell.
