Self-Hosted Main

Opnsense Unbound

2 instances of Adguard Home (VM and Raspberry PI with adguard sync) using DOH upstream servers (currently Cloudflare, Quad 9, and Mullvad). Works like a champ, have not touched it in over a year.

I use Unbound as a DNS resolver and pfBlockerNG for ad blocking. My firewall blocks external DNS, DoH, & DoT servers except for dns.adguard-dns.com, which I use on my phone.

I use NextDNS on occasion. I used to use pihole a while back during the “Covid years” but something it was blocking royally screwed up my kid’s Google Classroom submitted schoolwork, he was turning in empty assignments and we thought it was his fault but it wasn’t. Had to apologize to multiple schoolteachers and vowed never to use that piece of shit software again.

I use AGH on both of my servers at home and sync them with adguardhome-sync.

They are the DHCP assigned DNS servers for everyone who lives with us and all the services I run.

I use Adguard. I dumped pi-hole a long time ago and never looked back.

Straight into Pihole with Cloudflare upstream

Adguard Home with Unbound. And Unbound uses root.hints file to resolve

Edit: I use Hagezi Pro, Oisd.nl as blocklists as the are very well maintained

clients>pihole>unbound

I have a rather complex setup. I have a PiHole that is accessible over a VPN, but I only route DNS traffic over the VPN.

I stopped using pihole years ago because it didn’t support wildcards. Technitium DNS server is fantastic. The dev is super responsive and keeps things updated.

Client >> Pinole >> unbound but gonna take a look at Adguard now reading this thread.

AGH with upstream lookups over DoH, and adblock list from oisd.nl.

Split-brain topology to give internal IP in preference to public IPs for my selfhosted services, and selective routing of a defined set of domains to a geo-unblocking service so I can access things like BBC iplayer etc. from my home network.

Clients>Bind>pihole>unbound

I use nextdns as I can use that when mobile but if you want a local solution adguard home has DOH/DOT built in and a nicer interface than pihole IMHO

CoreDNS as my central DNS manager in my home(lab).

Currently two nodes are running CoreDNS with the same config for resilence. I really hate long DNS chains, because if something breaks in between, DNS is out ... wife and children scream ... me unhappy.

Current setup with five zones:

- .fritz.box - resolved to the provider-supplied router which also manages my network printer

- .home - forwarded to my UDM which runs DHCP in my home

- .lab.home - zone file which define s a wildcard to resolve all requests to my Traefik reverse proxy

- .consul - forwarded to Consul service catalog for service discovery

- . - everything else (internet) is either forwarded to AdGuard Home (and then to Cloudflare DNS) if the AdGuard service is running. If not, forward directly to the UDM. Nomad + Consul are amazing for this kind of templating and dynamic re-configuration.

Works quite well for me :-)

I use two Technitium DNS servers, the primary server runs in a container under Proxmox and the secondary as a failover on a Pi4. I only use Pihole for a handful of clients (mobile phone, FireTV etc.) these are assigned the DNS address from PiHole via DHCP, all other devices use the Technitium DNS directly. As internal domains I use the scheme "host.in.lan" and all devices (except servers) get their IP via DHCP (the Technitium DNS server also has this built in) and a DNS entry is automatically created for them via DDNS

I was using two instances of Pihole, one on a Pi and one via WSL on my Win10 host. Unfortunately my Win10 host no longer works, it’s randomly stopped and I haven’t had the time to try and fix it. I’ve got backups of the config luckily, but to be honest if I can do a more friendly local install with Adguard I’m probably going to give that a go on windows instead. Never tried it but I’m willing to give it a shot if it means it’s not going to break. My Pi install has been bulletproof so far and kept my network running whilst my Windows install has been broken.

Clients --> Windows Server 2022 DNS --> Pihole --> Internet

Clients (LAN or VPN) -> PiHole -> DNScrypt-proxy. All hosted on a RPi3 B+. So all my DNS requests are passing through my ISP encrypted.

Dual unbound servers running unbound-adblock in recursive mode with DNSSEC on, with a stubzone for my internal domain (*.lan) pointed at the dnsmasq server that handles dhcp and local DNS.

I wanted dns redundancy so at least "the Internet" would work if I was rebooting something, which the sub zone handles very well.

Dnsmasq is set to no upstreams, and authoritative for the domain. This gives me ddns for clients as well.

I did look into kea for DHCP and nsd for local DNS, but kea wasn't really ready to handle dual stack clients with the ddns updates. It was neat that you can run kea in a proper redundant config. Not sure I'd have been able to get the ddns updates to dual nsd servers working without a hidden primary, leaving me with a single point failure.

I have two piholes setup as full recursive dns servers (unbound) DHCP is handled by TP link Omada and the piholes are the two dns servers. The top of the DNS chain is cloudflare 1.1.1.1

I use technitium as the primary server, with a pair of backup servers running bind9.

The backup servers do zone-transfers from the primary.

for my home network, i use adguard in combination with my opnsense for dns.upstreams, if it needs to leave my network, are the usual suspects: google, cloudflare, and quad9 - selected based on performance

for my servers/domains i used to just be a regular BIND user, editing the zonefiles manually when needed.... but i have since switched my dns over to cloudflare because "easy and no maintenance"

(i might be one of the weird ducks in this sub: i still do my mailserver myself, but outsourced my dns to cloudflare...)

though, to be honest, there are quite a few additional reasons i did the cloudflare move:

• the use of their cdn
• hiding the actual server IPs
• using their zero trust

Clients -> dnsmasq -> PiHole -> Unbound

If you have active directory why not just use it's DNS server?

I've been using PiHole for years but just switched to NextDNS. Mainly because I use DNS to filter adult sites for my kids. NextDNS works regardless of the network they are on. I used to block YouTube etc at night but if we're are on holiday they get no filter.

I switched to AD Guard (at home) now as I can configure DNS over TLS for devices that only support regular DNS. So for example my kids TV talks to AD Guard and then AD Guard looks at the MAC address and sends it down a specific DNS over TLS address. So that TV gets the filters of my kids NextDNS profile.

Adguardhome + Opnsense

I run 2 pihole containers on my k8s cluster. They serve up DNS to the rest of my network. This is extremely easy as I can just use helm to launch the pihole containers into two different namespaces using 2 different site specific files. Then I use teleport to keep them in sync when I change something, which is seldom. I run 2 because DNS is important and I like automated patching / reboots. This requires I have redundant services.