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
After much suffering with local zones (mainly due to stubborn devices ignoring dns servers coming via dhcp and retarded corporate vpn messing with resolv.conf) I just use xxx.local.mydomain.tld with a small script that parses the leases files and updates the data via cloud flare api.
I ended up doing a similar thing for the same reasons, too many things ignoring my local dns. I ended up creating a subdomain for my house where all the A records had internal ips. I gave out fixed leases to the things with names though instead of dynamic dns updates.
I have static ips for the server-ish things and few important devices too, but for the rest (swarm of shellys, esp32, etc.) I'm too lazy to maintain the list =)
Using a real domain also lets you get Let's Encrypt TLS certificates for the subdomains, by using DNS challenges.
I do the same thing - I use
xxx.int.example.com
andxxx.vpn.example.com
for internal IPs and VPN IPs respectively.