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
A .com domain should be under USD $12 a year with WHOIS privacy included. If someone is charging more than that, they are ripping you off. Most web or VPS hosts will charge a significant markup if they sell domains. Make sure you check the renewal price too. Some registrars will give you the first year cheap, then charge significantly more to renew it.
Cloudflare is the cheapest, but they force you to use their DNS servers. Porkbun is a dollar more, but you can use your own DNS if you want to.
I have my domain with Cloudflare too, and at this point, I’m not aware of these DNS servers. Can someone explain it a bit? I know what DNS is, but I don’t understand what’s the use case for having them elsewhere. I’m not to argue, just didn’t know where to register a domain, so I went with them. I’m concerned with the future of the domain either, but don’t understand the issues at this early point.
The DNS authoratative servers are what hold all of the records for your domain. With Cloudflare, you are stuck with theirs. As for why you want to use a different one, maybe you need more than the 200 records Cloudflare limits you to. Maybe you don't like the way their API works for automating updates. Maybe you don't want to set up all of your records all over again if you transfer your domain to another registrar. Maybe you just don't like Cloudflare.
Thanks! It’s a bit more clear now.
To contribute to the discussion, I remembered that with Squarespace (my previous registrar), I had unlimited redirects, which I used heavily. I am not really sure about the unlimited part, perhaps that was hidden somewhere in the interface, and they have limits, and I just never saw them. But I remember Cloudflare communicated I have like 10, so I decided to not use it for nice-to-have but not really needed things. E.g. I used a subdomain for a blog, and created redirects for typical misprints in my name. Was handy, but not really needed. I should have document this, but I was too busy at the time, and now, almost a year later, I don’t really remember. There were differences with Cloudflare and Squarespace.
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!