this post was submitted on 31 Jan 2024
167 points (97.7% liked)

Selfhosted

40041 readers
728 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] SnotFlickerman@lemmy.blahaj.zone 44 points 9 months ago* (last edited 9 months ago) (9 children)

Looks like *.lair is still a great one for a local TLD.

Just rock your "Evil.subterranean.lair" people.

You could also go for "Wicked.volcano.lair"

Or even "morallywrong.commercialrealestate.lair"


Also, anyone taking bets on how many "Internal" TLDs are gonna be used for porn?

[–] Robert7301201@slrpnk.net 57 points 9 months ago (7 children)

Very few as this ruling would reserve .internal for local DNS only and forbid it at the global level. This is ICANN's solution to people picking random .lan .local .internal for internal uses. You'll be able to safely use .internal and it will never resolve to an address outside your network.

[–] KingThrillgore@lemmy.ml 19 points 9 months ago (6 children)

.local is recommended for use with mDNS/Zeroconf

[–] Robert7301201@slrpnk.net 9 points 9 months ago (1 children)

Yes, you're right, RFC 6762 proposes reserving .local for mDNS. I was not aware of this until you brought it up, hence the dangers of using using TLDs not specifically designated for internal use.

[–] KingThrillgore@lemmy.ml 9 points 9 months ago* (last edited 9 months ago) (1 children)

Yes, you’re right, RFC 6762 proposes reserving .local for mDNS. I was not aware of this until you brought it up, hence the dangers of using using TLDs not specifically designated for internal use.

I had actually used .local for years until I caved upon knowing, and bought kingthrillgore.name and used it both for my web sigh and my local domains. For most people, this is an unnecessary cost. We should really approve adding .lan and .localhost to ICANN as reserved domains as well.

[–] Robert7301201@slrpnk.net 7 points 9 months ago (1 children)

.localhost is already reserved for the loopback, per RFC 2606, but I agree with you in general. A small network shouldn't have to have a $10-15/year fee to be compliant if they don't want to use a domain outside their network.

As other posters have mentioned, .lan .home .corp and such are so widely used that ICANN can't even sell them without causing a technical nightmare.

[–] conorab@lemmy.conorab.com 5 points 9 months ago (1 children)

People who do not wish to buy a GTLD can use home.arpa as it is already reserved. If you are at the point of setting up your own DNS but cannot afford $15 a year AND cannot use home.arpa I’d be questioning purchasing decisions. Hell, you can always use sub-domains in home.arpa if you need multiple unique namespaces in a single private network.

Basically, if you’re a business in a developed country or maybe developing country, you can afford the domain and would probably spend more money on IT hours working around using non-GTLDs than $15 a year.

[–] sir_reginald@lemmy.world 2 points 9 months ago (1 children)

come on, setting up your own DNS is not difficult at all. For my home network, it's running in a Raspberry Pi, but before that I ran it locally on my desktop. There's no way I'd spend 15$ a year to resolve internal addresses.

Sure, you have to be careful with the TLD you choose, but I believe that if the ICANN were to create the .lan TLD, it would be all over the internet first.

[–] conorab@lemmy.conorab.com 1 points 9 months ago

Buying your own domain often includes DNS hosting but that’s not really the point unless all you’re doing is exclusively running an externally-facing website or e-mail. The main reason for buying a domain online is so everybody else recognises you control that namespace. As a bonus, it means you can get globally-cognised SSL certificates which means you no longer have you manage your own CA and add it’s root to all the devices which wish to access your services securely. It’s also worth noting that you cannot rely on external DNS servers for entries that point to private IPs, because some DNS servers block that.

load more comments (4 replies)
load more comments (4 replies)
load more comments (5 replies)