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:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
I would not expect any issues.
From the point of view of DNS, a name is a name.
You can never tell what weird restrictions any given software is going to place on you (there were a lot of forms that did not like TLD with more than 4 characters, 20 years ago or so). But it's only $1, so worth experimenting, IMHO.
Please let us know if there are problems!
Self reply as a follow up.
I use nom.es for DNS experimentation. These are like $3 a year or so, and work fine.
I miss DotTK, which was dodgy and didn't support DNSSEC, but was actually free. 😅
This is definitely one of those things I didn't know that I didn't know. What kinds of restrictions are there on domains, generally? I thought I could just get the cheapest domain that somewhat resembles the name I was going for. I'm not in the market for a domain yet, but I suspect I will be in a few months.
There used to be restrictions on a hostname.
These had to start with and end with a letter or number, and have only letters, numbers, or a dash. (I heard that originally hostnames had to start with a letter, but 3M got that changed. This might be an urban legend.)
That's a common restriction for a name still.
Things get funky when you want non-ASCII names - like if you want a cyrillic or Greek name - as registries often limit the allowed characters to limit "isomorphic attacks". That's where you use symbols that look the same to trick people into thinking they're going to another site, like using a 0 instead of an O, or a l instead of an I.
None of this will apply to the XYZ domains that give you a number.
One other issue that might impact you is if you try to connect using only a numeric name. Some tools will interpret such a name as an IPv4 address. Easily solved by using the full name, but weird and confusing if it happens to you unexpectedly. 😅
Thanks. Yeah, some of the ones I was targeting were cheap domains like ampersandrew.xyz or whatever. I don't think I'd be doing anything so fancy as to violate the above. What does the OP's "1.111b class" mean?
Wiki 1.111b class https://en.wikipedia.org/wiki/.xyz
E: sorry no experience with it. Fqdn are just labels, so in theory it doesn't matter.
If the feature set is limited (I.e. mx records or aliases) it could be a problem.
Wiki states, that blacklisting is an issue (could be relevant for Mail servers), not sure if this affects self-hosted web pages (browser asks clearing instance about known bad websites).
yeah i use one for jellyfin its fine 👍
Doubt you would have issues. Just on April fools I bought an xyz domain and pointed it at my unraid server to host a site for my wife to prank her coworker. It all worked just like normal.
As you said, it's ten bucks for a decade.
I've use mine for years with no issue, and if any it's my fault not the domain.