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.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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
Here is a somewhat simplified explanation
When you are registering a domain you are essentially just creating a NS record:
mydomain.com NS
Then when a resolver is asked a question like what is the A record for myserver.com it goes and asks the tld server (.com) what is the NS record for mydomain.com. the tld then responds with the nameserver ip. Then the resolver will query the nameserver directly for the A record of mydomain.com
In practice there is a ton of caching going on here, but that's the broad strokes
Thanks! I haven’t thought of com as being the real TLD, actually!