this post was submitted on 24 Jan 2026
141 points (98.6% liked)
Selfhosted
60210 readers
947 users here now
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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
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!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
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!