I use Pi-Hole unbound, and I really like it. However, Technitium seems to be the new favorite and has a lot of bells and whistles that Pi-Hole doesn’t. I haven’t run Technitium basically because Pi-Hole fits my needs. If I were just starting out, I would probably consider Technitium.

I am one of those zillion users. I love it.

It’s fine, did the job for me at the time. Just wanted the ad and nasty blocking. Keeping it and the filters up to date is easy.

Now have a pfSense box with pfBlocker-NG, which does essentially the same thing. Also runs Snort as an additional layer, and makes penning in IoT stuff possible.

My pi 1b handles the internal DNS for my game servers, which at this point is actually just minecraft because PSO:BB was way harder to setup than I thought. It works and it is extremely easy and it still holes all the tracking stuff too.

I mostly like it, but over the last few months I’ve had my pihole die randomly during the day, which killed my home network, and I had to walk my partner through rebooting everything.

I’ve now got redundant pihole instances, but I’d really like to know what is going wrong with pihole. Its impossible to replicate, and very sporadic.

I have that virtualized, times three. Two to have a failover, and third one with different settings for my kids (cloudflare’s family dns)

@bernhoftbret@lemmy.world pihole is great. I use AdGuard now but either is good. The important thing is having a dns server at home

I use a RPi 5 running docker for: Pi-Hole, Jellyfin, Home Assistant, Heimdall. Works great, and there’s still capacity left to add more services.

I have pihole running on an old Raspberry Pi B and it just chugs along. Except for the wonky update they put out a few months ago. That took some cleaning up after.
I check the dashboard a few times a day and it’s a good way to notice network issues and misbehaving programs.
I’m also running it through cloudflared to encrypt the requests, in case my ISP is snooping on them.

I use technitium, but there is nothing “wrong” with using a pihole. I used to run several (containers, plus one physical), and have set up quite a few for family and friends.

PiHole 4b powering my home DNS. Been running for ~4 years as of next month (and still on the original SD card I installed it to!). 100% recommend.

pihole has got the best UX for DNS management hands down. it’s easy, not overly complicated, and perfect for entry-level selfhosting.

the fact that it actively blocks ads is a bonus.

Indispensible.

A longer answer would come out of: “What do you think of a home lab environment without Pi-Hole?”

I love it! It took me a bit to iron out all the kinks with my network, but I am completely happy with it now.

Sadly, it was very bad. I tried it about five years ago on a Pi 4. In less than a year, the Pi crashed five or more times. Once it was due to a faulty SD card, and on several occasions it was due to other software on the Pi crashing. Each time, the internet went down, which made my family unhappy, especially when I was not at home and could not fix it.

I also saw little benefit as I already block ads on all my devices, and my smart home stuff has no internet access at router level.

I haven’t tried it since. Should I try again now with redundancy? What are the benefits?

Technitium DNS Server is a bit more feature rich but honesty I would just run a DNS filter on your router

I ran it on a Pi Zero W for a bunch of years, and it was as stable and problem free as it gets.

Early this year I swapped out my wifi/router for a minipc running OPNsense. I retired the pihole since OPNsense has Unbound built in.

I started playing with it, but decided that DNS was slightly lower level than I wanted to host myself (personal opion, more power to you if you disagree). Instead, I use NextDNS which gives me great control down to individual devices, blocks ads and malware, and doesn't bring down the internet for my entire home if I have a faulty power supply or SD card or whatever.

I set up split dns using a phone earlier this year, and it’s been fantastic

I like it but just not on a Pi. I found it too unstable. I found it easier to host in a docker container.

Although these days i just use blocklists on my router.

I preferred AdGuardHome over PiHole, but currently my servers are collecting dust as I need to get electrical work done before I can hook them up.

It really sucks…

Yes.

Maybe a controversial take, but I like pihole for blocking only - I have a pair of powerDNS servers set up for my internal name resolution. They recurse to Pihole, but can fall back to internet DNS servers if Pihole isn’t responsive.

I tried pihole for local resolution and found it to be a fairly large pain to automate. Plus kubes has PDNS hooks for auto-updating DNS entries.

I run Pi-Hole in a docker container on my server. I never saw the point in having a dedicated bit of hardware for it.
That said, I don’t understand how people use the internet without one. The times I have had to travel for work, trying to do anything on the internet reminded me of the bad old days of the '90s with pop-ups and flashing banners enticing me to punch the monkey. It’s just sad to see one of the greatest communications platforms we have ever created reduced to a fire-hose of ads.

I used pihole for years, but the recent updates made me look for alternatives. There was a major (v6?) update fuckup, but also some random freezes and block lists going missing…

Looking for alternatives, I tried out Technitium. Extremely easy to set up, rock solid, running steady for about 6 months (with frequent updates), and they recently introduced built in high-availability.

Depends on how you do it and what you need from it. I’ve actually moved on from my Pihole instance, for reasons I’ll get into later.

The broad appeal of using Pihole for DNS in a homelab is the ability to route services from domain names on the local host. This can be really useful, especially for “hacking” service availability onto other unintended devices. Additionally, it can be nice for less tech-savvy users who might not be comfortable editing /etc/hosts or just want to check out a service on their phone web browser.

I would generally recommend using an isolated device for Pihole needs; If you’re doing work on your home server, you’ll probably want all users on your service to keep their internet connection working to not be a burden to others living in your household (if you have others). A raspberry pi is a really good target for a pihole, and even a cheap old/used one from the interwebs can serve you well (I was using one recently on a pi3b and it was no issue.) Keep in mind that you can’t really do fallback dns configuration unless you’re ok with losing the key feature of pihole (blocking ads and redirecting domains). Notably, I’m actually not a proponent of running all services on individual compute units generally, I just think DNS is special and you don’t really want to tie it into docker services to keep a separation between the services and the server, so to speak.

This brings me to the second feature: adblocking. This one is really a mixed bag. Ultimately, I turned this feature off only because it doesn’t work for the websites that have arguably the most ad content (youtube, twitch) and really only serves to hurt the smaller players. Sometimes it’s great for blocking things like SmartTV advertisements or data encroachments, but it’s very hard to block ads from a web domain in a way that doesn’t outright block the service itself (so blocking youtube ads without blocking youtube is, seemingly, a fools errand.) I’m willing to hear other people’s opinion on this, I just couldn’t get this working to a satisfactory degree.

I’ve abandoned Pihole as a local dns resolver. This is because Tailscale suits my needs and also allows me out-of-house connectivity to things like my music or personal data so my phone never goes out of communication with my home network. When you use tailscale at home, it’s generally really good about routing that through your local network instead of the relay, so there shouldn’t be that many downsides. Note, I say generally, because there have been times where it goes through a relay unexpectedly which I haven’t solved yet (this is likely a local router configuration issue, anyway…)

I notice that you’re already familiar with Pihole, but just thought that it would be best to “explain” my thoughts on it in the form of a recommendation/editorial form.

I switched to github.com/0xERR0R/blocky

Pihole was fine, but had features I didn’t care (mostly UI). Blocky is much smaller and lightweight

To anyone having issues running on a pi it’s likely either or both of the following item -cheap 5v power supply. Yes you can use an old phone charger but it won’t cut it for long term usage. Get a quality unit or better yet the branded pihole charger. We ended up with a Poe hat that it runs off. Sorted Ethernet and power supply.

-memory card. Buy a quality, fast card and you will be fine.

Going on 8 years with my current pi setup. One failure around 6 years in which was the memory card

I run 2 instances of pihole/unbound as lxcs on my main server and local back up, works great.

If I didn’t have the two big boxes I’d use my pi4/zero2 to run two instances of pihole/unbound.

If I didn’t have my pis, I’d run 2 instances of pihole/unbound on literally anything I could install it on.

What I’m saying is that I consider pihole/unbound to be essential infrastructure at this point. I’m also trying to say I’ve broken my only instance of pihole enough times to understand the importance of redundancy.

I use Pis as a (sort of) hardware key to get family and friends onto my Tailscale VPN. They all have pihole too. I haven’t convinced any of them to get a pi0 as a redundant box, but I’m sure they’ll learn eventually too. No doubt it’ll be my problem.

The number one rule of selfhosting unbound. Make two.

You won’t be happy one morning if you don’t. I run unbound with adblocking on OpenWRT, but if my router dies, my whole network does anyway, so… Eh.

I just use adguard home. Worker a little better in my docker setup.

I run pihole without any problems as a docker container. I assume you want to ask how well it works to add custom records, because that’s what you usually do with a dns server.

Adding single records with the web ui works just fine. However, adding wildcards isn’t possible. So you end up attaching a terminal to your container and adding dnsmasq configs yourself. This is a bit poor.

On the other hand: How often do you need to add wildcards? I needed like 2 entries since I set up pihole a few years ago.

I run it in a VM and it’s great

I prefer using NextDNS, so that it works wherever I am

I run Pihole on physical Pi’s and once configured to my liking has been quite nice. I’ve even had family compliment that they miss the ad blocking when they leave the home :)

Doing it.
If it works? Why not

I have run Pihole on 2 physical Pi 4s (DietPi OS) with config sync for 3 years now. Core to the house. Very reliable.

I use it on a Raspberry Pi 2B and Orange Pi Zero, both work wonderfully for the task, and it looks like Pi-Hole can work fine even on a router. Both of my SBCs are passively cooled, that’s why I decided to comment on the photo: you don’t need a computer this powerful to run it. As far as I remember, my very first Raspberry Pi (v. 1B or something like that) handled this task very well too. I temporarily retired that SBC in favour of Orange Pi Zero, so I cannot say for sure, but I think that computer had no issues with being fast enough for Pi-Hole. Really, give it a try if you didn’t, it’s ‘install once and forget’ type of software. Perhaps it should be updated periodically, but I don’t manage that. The only nuance with it, you need to have two computers, for the redundancy. Otherwise you’d be having downtimes when you need to turn off the SBC, or even reboot it.

I’m running one Pi-hole, but not on RPi. One is an LXC container on my Proxmox host, another is on dedicated Dell Wyse thin client box.

Not a fan of Pi-hole itself, but other than that,why not?

(Technitium DNS has some advantages down the road)

I run a pi-hole on a pi 3 and another in a container in docker. Something rarely goes wrong with both and I have a script that sync them.

I replaced their google with searxng, but in the end, they needed ads for their free to play games, so I had to turn it off for them.

I installed a Pi-Hole largely to serve as a local DNS, but enabled the ad-blocking 'cause it seemed silly not to. My wife got very upset. Apparently she likes the ads.

With that aside though, it seems to work quite well. Just make sure to (a) use a reasonably-powered device (my Pi Zero appears to be taxed by it) and you should probably use an Ethernet connection 'cause my Pi Zero regularly flakes out so DNS requests fail due to the IP being “unreachable” for a half second.

It’s great. Gets things done. I even have it for my office. About 20 people there.

I had a look at it but didn’t use it for longer, I used adguard later in a lxc container later, since i didn’t see a point in using a different device, right now the adguard is running as a service on my opnsense so i don’t have to rely on something other than the router for internet. I like the option to block on a dns level, and to be fair it’s always a similar set of blocklists that can be used, the major difference is in the preselection. right now I could probably switch back to the default opnsense dns server and add the lists there, only losing the info on what has been blocked.

PiHole works great. I get 20% of requests denied and it really helps keep ads and unwanted sites to a minimum. It was easy to setup. I just update it via ssh once every 60days or so.

The stats are kinda revealing also as to the sites the household uses .

RPI is great but you have to consider SD card wear. It will not last you forever and at one point will fail. At that moment your dns is no more.

Anybody got the feeling some games may be negatively affected by a PiHole ?

It’d not really the reason I stopped using it but I suspected that some games didn’t like it when PiHole was up…

Anyway this post motivated me to reinstall my RasPi.

I run pi-hole in docker in the background of our libreelec (Kodi) home entertainment system and it works great. It’s a MUST if you have kids, my son has more freedom to use the internet since I know he is mostly covered by extensive block lists. Using raspberry pi 400, we watch Netflix, play Nintendo games, watch YouTube and have a family hard drive for shared photos and files.

I ran pi-hole on my NAS. Then I pointed my router at it to make it the DNS for my whole network. The only problem was it would create issues when I had a power outage. If things didn’t start up with the right timing they would get wonky and certain devices would report as not having Internet.

That’s why I bought an OpenWRT One so I could install an equivalent to pi-hole on in directly. Though I hit a snag with that and don’t currently have that running.

I haven’t noticed much of a difference without the pi-hole running (my NAS is dead right now). I think some of my devices had their own DNS settings so they weren’t using the config from the router.

@bernhoftbret Others have mentioned already, the main issue being if the network comes up before the Pi-Hole does, some devices will be confused.

One possibility to mitigate this, you can get a UPS for your Pi that uses one or more 18650 batteries, fairly cheaply.

I also thinks to myself, some routers can surely be made to act as a DNS cache for the Pi-Hole, and thusly, maintain a working table through disconnections/powerlosses. Whether that applies depends on each case, the hardware and the wetware.

I used pihole for many many many years, never go back ever again. database crashes, random freeze, UI broke just from an API call and sometime just randomly. Tried on Pi2, Pi3, Pi4, VMs, the result was always the same. then I switched to adguard home, no issue ever since. I’m using it for:

1. DNS level adblock
2. Local DHCP server
3. DNS server for routing home stuff As DNS and DHCP is kinda important, I have a separate VM just for adguard and docker registry, 512-2G ram. Then I have 2 VMs running alpine as docker swarm, 8Gb each. It’s important to make sure even if your “main” infra goes down, you will still have internet to search and debug - hence the separate VM. Also using an NFS share for persistent storage for the data.

Success story here. 6+ years running pihole on proxmox as my primary DNS for everything on my network. It’s never missed a beat, never crashed. I update infrequently. It’s just good software.