Selfhosted
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
- 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!
view the rest of the comments
I am definitely not the best at networking, but can't you do that through your current dhcp client?
I think he wants to do server side, not client. And that the dns filter picks up those ip addresses or ranges, and let some through.
If I keep UniFi DHCP then Pihole will not show individual clients, making it hard to put blocks on those individual clients.
In the past, the only solution I found was to let Pihole provide DHCP instead of UniFi.
Oh that's just a config change needed, in your DHCP server you need to set the DNS server (option 6) to the Pihole/adguard IP.
Then you'll have Unifi DHCP but with clients using pihole/adguard for DNS directly so you get per-client blocking and proper stats.