176
Self-Hosting a DNS Sinkhole is really important
(www.wired.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 16 Oct 2026
176 points (97.3% liked)
Selfhosted
63007 readers
1623 users here now
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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
The main way is it has a built in recursive DNS server so you don’t have to duct tape Pi Hole and Ubound together
I never understood pihole in the first place. It's just a fancy web interface you do never look at if the thing does its job quietly in the background. And unbound alone is perfectly able to use blocklists with one line of configuration (and an onliner script to convert the common lists into the right format).
@Ooops @EncryptKeeper
Those scripts never worked for me....... so pihole-unbound to the end......xddddddd
My "script" to update the blocklist from time to time was literally
curl <blocklist1 link> > templistcurl <blocklist2 link> >> templistgrep '^0\.0\.0\.0' templist | awk '{print "local-zone: \""$2"\" always_refuse"} > blocklist.confsystemctl restart unbound.serviceand an
include blocklist.confat the bottom ofunbound.conf(awk to convert it from the "0.0.0.0 " format to "local-zone: always_refuse").Because you have to mess with it all the time. It’s easier to get in and get out to make changes with the nice interface. It’d be different if it was set it and forget it but realistically it’s not.
It literally is a cron job or systemd timer to load an updated blocklist from time to time and I haven't looked at it for years (well... other an changing a path when I switched from unbound to dnsproxy, because that one is even simpler, doesn't even need a config other than a few parameters at startup and can provide DoH, DoT and/or DoQ access for when I'm not at home)