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
DNS points to the domain. Then you configure the subdomain on the same IP. Maybe I'm missing something, but this is how I understand subdomains.
Decent DNS providers allow you to create NS records for subdomains.
This delegates the subdomain and all of its subdomains to another DNS.
Useful for companies that want to control their own records, but might want to allow a group of developers control over app.example.com and all subdomains, without the developers having to pester the company for record updates.
Also used for acme-dns, which is a self hosted DNS designed to only deal with txt records for acme DNS challenges (ie lets encrypt).
Means you can limit the possible disaster of the DN API keys being leaked (an attacker can only generate TXT records, instead of rewriting all your DNS records)