Hey guys, I recently bought an orange pi zero 2 and, as the title suggests, I want to put an ad blocker on it. Those are the options. I also will put openvpn for external connection to my network.
Does anyone have experience with them? What would you suggest?
I also started on pihole, but switched to Blocky because Blocky is way more DevOps friendly (I run this stuff on microk8s on a Pi cluster).
Then I just ditched it altogether and now use NextDNS. Well worth paying the small fee for. But you obviously don’t get the same DIY satisfaction out of it.
Well it’s a service I’m paying for, so yes a bit of trust is required. Their privacy policy looks decent as well. As it stands, I trust them more with it than I would my ISP, Google or Microsoft.
You can choose what region to log to (I chose Switzerland) and you can also configure the retention period.
Tbh I just run pihole as a background service on my PC since I can’t easily access router to change DNS for the whole network anyway. It never seemed that much work, what devops issues were you running into with it and Blocky to justify paying a service for it?
My main issue with PiHole was that the container wouldn’t work on later versions of Ubuntu for some reason (if I remember correctly, anything later than 18.04). I never did figure it out. The other reason was since I was running it in Kubernetes, the whole point is to have multiple replicas running for redundancy, but PiHole’s UI is coupled with its backend DNS service so if you have 3 PiHole instances running, you had 3 GUI instances as well. You could load balance the DNS requests (I used MetalLB), but visiting the UI was pointless.
Also, the config was very scripty and not really container friendly - I mean it worked but it wasn’t designed as a cloud native application. No fault of its own but it didn’t really suit the way I like to do things.
Enter Blocky, which doesn’t have a UI and has a very simple YAML config that is easily mounted to a container. It scaled much easier, used way less resources and was just simpler to manage. It was really exactly what I was looking for.
However, ultimately running the DNS service for my house out of a Pi cluster wasn’t really my best idea. It has to work 100% of the time, and I would have frequent outages. We are a family of 5, so imagine lots of ‘Dad! The TV’s not working!!’ and stuff like that every time. This thing was a pet project, and I didn’t have it set up as a ‘production’ service, which is what it really should be. Sometimes the metallb pods would fall over, or the kubernetes TLS certificates would expire for the cluster, etc. I didn’t have proper monitoring and alerting setup, etc. I just couldn’t be bothered putting the effort into it that it required.
NextDNS does exactly the same thing, with probably even better controls, is more reliable, has great logging and costs bugger all.
EDIT: meant to add, I used it for more than just adblocking, but also for parental controls. NextDNS is great for that as well.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
I also started on pihole, but switched to Blocky because Blocky is way more DevOps friendly (I run this stuff on microk8s on a Pi cluster).
Then I just ditched it altogether and now use NextDNS. Well worth paying the small fee for. But you obviously don’t get the same DIY satisfaction out of it.
But NextDNS is closed source isn’t it? Personally I wouldn’t trust proprietary software with my entire DNS request history.
Well it’s a service I’m paying for, so yes a bit of trust is required. Their privacy policy looks decent as well. As it stands, I trust them more with it than I would my ISP, Google or Microsoft.
You can choose what region to log to (I chose Switzerland) and you can also configure the retention period.
https://nextdns.io/privacy
Tbh I just run pihole as a background service on my PC since I can’t easily access router to change DNS for the whole network anyway. It never seemed that much work, what devops issues were you running into with it and Blocky to justify paying a service for it?
My main issue with PiHole was that the container wouldn’t work on later versions of Ubuntu for some reason (if I remember correctly, anything later than 18.04). I never did figure it out. The other reason was since I was running it in Kubernetes, the whole point is to have multiple replicas running for redundancy, but PiHole’s UI is coupled with its backend DNS service so if you have 3 PiHole instances running, you had 3 GUI instances as well. You could load balance the DNS requests (I used MetalLB), but visiting the UI was pointless. Also, the config was very scripty and not really container friendly - I mean it worked but it wasn’t designed as a cloud native application. No fault of its own but it didn’t really suit the way I like to do things.
Enter Blocky, which doesn’t have a UI and has a very simple YAML config that is easily mounted to a container. It scaled much easier, used way less resources and was just simpler to manage. It was really exactly what I was looking for.
However, ultimately running the DNS service for my house out of a Pi cluster wasn’t really my best idea. It has to work 100% of the time, and I would have frequent outages. We are a family of 5, so imagine lots of ‘Dad! The TV’s not working!!’ and stuff like that every time. This thing was a pet project, and I didn’t have it set up as a ‘production’ service, which is what it really should be. Sometimes the metallb pods would fall over, or the kubernetes TLS certificates would expire for the cluster, etc. I didn’t have proper monitoring and alerting setup, etc. I just couldn’t be bothered putting the effort into it that it required.
NextDNS does exactly the same thing, with probably even better controls, is more reliable, has great logging and costs bugger all.
EDIT: meant to add, I used it for more than just adblocking, but also for parental controls. NextDNS is great for that as well.