view the rest of the comments
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:
- 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!
By adding do you mean blocking it in pi-hole or somehow redirecting it to your pi-hole dns server?
I currently have it blocked in my router and can confirm this by trying to ping 8.8.8.8 without any response. If you mean redirecting to your pi-hole I would really like to know how to do it
I didn't add it to any lists, but to the network interface itself. You know the output of
ip a
? The one pihole listens on (wg0
in my case, because wireguard) has something like, say,10.0.0.1
, but also8.8.8.8
. So when a DNS packet is spit out by chromecast to go to 8.8.8.8 UDP port 53 - my pihole happily answers that request. You could also do a separate unbound instance on a new virtual interface with a quad8 ip and just forward everything to pihole, if you fancy.