this post was submitted on 08 Aug 2024
499 points (99.2% liked)

Selfhosted

39435 readers
2 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
top 50 comments
sorted by: hot top controversial new old
[–] [email protected] 159 points 3 months ago (2 children)

It would have been nice if they came up with something shorter like .lan.

[–] Deebster 100 points 3 months ago (1 children)

Oh, that's LAN - I thought you'd put ian and I was trying to get the joke. Stupid sans-serif fonts.

load more comments (1 replies)
[–] [email protected] 52 points 3 months ago (1 children)
[–] [email protected] 44 points 3 months ago (3 children)

You go to networking jail for that.

[–] [email protected] 20 points 3 months ago (2 children)

Shit, let's hope the ICANN cops don't find me out then... I've been using it for years!

[–] [email protected] 16 points 3 months ago (2 children)

"I hereby sentence you to two years on your own VLAN with no gateway"

load more comments (2 replies)
load more comments (1 replies)
load more comments (2 replies)
[–] [email protected] 105 points 3 months ago (17 children)

Sorry. I chose .local and I'm sticking to it.

[–] [email protected] 56 points 3 months ago (3 children)

I switched from .local to .honk and I'm never looking back.

load more comments (3 replies)
[–] xcjs 30 points 3 months ago (4 children)

I was using .local, but it ran into too many conflicts with an mDNS service I host and vice versa. I switched to .lan, but I'm certainly not going to switch to .internal unless another conflict surfaces.

I've also developed a host-monitoring solution that uses mDNS, so I'm not about to break my own software. 😅

[–] [email protected] 18 points 3 months ago (1 children)

.internal takes to long to type

[–] xcjs 10 points 3 months ago

Yeah, that's why I started using .lan.

load more comments (3 replies)
[–] [email protected] 26 points 3 months ago

It's also second only to .com in terms of query volume in ICANN's Magnitude statistics with 980 mil vs .internal's 60 mil. Not sure if that makes it a de facto standard, but it's close.

[–] [email protected] 21 points 3 months ago (2 children)

I went with .home and so far the problems are within reason

load more comments (2 replies)
load more comments (13 replies)
[–] [email protected] 74 points 3 months ago (6 children)

It should be reserved for sex toys.

Just saying.

[–] [email protected] 21 points 3 months ago (2 children)

What are you doing step-LAN?

load more comments (2 replies)
[–] [email protected] 12 points 3 months ago (2 children)

I used to wonder why porn sites aren't required to use '.cum' instead of '.com'...

[–] [email protected] 10 points 3 months ago (1 children)

The original 3, “.cum”, “.nut”, and “.orgasm”.

load more comments (1 replies)
load more comments (1 replies)
load more comments (4 replies)
[–] [email protected] 50 points 3 months ago (29 children)

Browsers barf at non https now. What are we supposed to do about certificates?

[–] [email protected] 27 points 3 months ago (1 children)

If you mean properly signed certificates (as opposed to self-signed) you'll need a domain name, and you'll need your LAN DNS server to resolve a made-up subdomain like lan.domain.com. With that you can get a wildcard Let's Encrypt certificate for *.lan.domain.com and all your https://whatever.lan.domain.com URLs will work normally in any browser (for as long as you're on the LAN).

[–] [email protected] 24 points 3 months ago (9 children)

Right, main point of my comment is that .internal is harder to use that it immediately sounds. I don't even know how to install a new CA root into Android Firefox. Maybe there is a way to do it, but it is pretty limited compared to the desktop version.

load more comments (9 replies)
[–] BlueBockser 21 points 3 months ago

Nothing, this is not about that.

This change gives you the guarantee that .internal domains will never be registered officially, so you can use them without the risk of your stuff breaking should ICANN ever decide to make whatever TLD you're using an official TLD.

That scenario has happened in the past, for example for users of FR!TZBox routers which use fritz.box. .box became available for purchase and someone bought fritz.box, which broke browser UIs. This could've even been used maliciously, but thankfully it wasn't.

[–] [email protected] 14 points 3 months ago

Either ignore like I do or add a self signed cert to trusted root and use that for your services. Will work fine unless you're letting external folks access your self hosted stuff.

[–] rushaction 10 points 3 months ago (4 children)

Quite literally my first thought. Great, but I can't issue certs against that.

One of the major reasons I have a domain name is so that I can issue certs that just work against any and all devices. For resources on my network. Home or work, some thing.

To folks recommending a private CA, that's a quick way to some serious frustration. For some arguably good reasons. On some devices I could easily add a CA to, others are annoying or downright bullshit, and yet others are pretty much impossible. Then that last set that's the most persnickety, guests, where it'd be downright rude!

Being able to issue public certs is easily is great! I don't use .local much because if it's worth naming, it's worth securing.

load more comments (4 replies)
load more comments (24 replies)
[–] [email protected] 34 points 3 months ago (5 children)

Why do I care what ICANN says I can do on my own network? It's my network, I do what I want.

[–] [email protected] 35 points 3 months ago (12 children)

Try using .com for your internal network and watch the problems arise. Their choice to reserve .internal helps people avoid fqdn collisions.

See also https://traintocode.com/stop-using-test-dot-com/

load more comments (12 replies)
[–] [email protected] 20 points 3 months ago (1 children)

Certain domain names are locally routed only. So if you use internal or local as a tld, you can just assign whatever names you want and your computer won't go looking out on the internet for them. This means you and I can both have fileserver.local as an address on our respective network without conflicting. It's the URI equivalent of 192.168.0.0/16.

load more comments (1 replies)
[–] [email protected] 18 points 3 months ago

YouCANN do anything you want?

load more comments (2 replies)
[–] [email protected] 32 points 3 months ago (2 children)
[–] [email protected] 28 points 3 months ago (1 children)

But what if your name is not Ian...

[–] [email protected] 10 points 3 months ago

Then change it Ian!

load more comments (1 replies)
[–] [email protected] 28 points 3 months ago (2 children)

That's good, I never liked the clunky .home.arpa domain.

load more comments (2 replies)
[–] [email protected] 18 points 3 months ago

Took long enough

[–] [email protected] 17 points 3 months ago (6 children)

Thanks but I hardly needed anyone permission to not use that. .local still works just fine.

[–] [email protected] 17 points 3 months ago

Except when it doesn't. It can have issues around multicast dns.

[–] [email protected] 14 points 3 months ago* (last edited 3 months ago) (2 children)

I've had issues with .local on my Android device. Straight up doesn't work. I had to change to .lan

load more comments (2 replies)
load more comments (4 replies)
[–] [email protected] 16 points 3 months ago (3 children)

Interesting. I've been using ".home.arpa" for a while now, since that's one of the other often used ways.

load more comments (3 replies)
[–] [email protected] 15 points 3 months ago

Missed the opportunity for .myshit.

[–] [email protected] 15 points 3 months ago* (last edited 3 months ago)

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

Fewer Letters More Letters
CA (SSL) Certificate Authority
DNS Domain Name Service/System
HTTP Hypertext Transfer Protocol, the Web
HTTPS HTTP over SSL
IP Internet Protocol
SSL Secure Sockets Layer, for transparent encryption
TLS Transport Layer Security, supersedes SSL
VPN Virtual Private Network

6 acronyms in this thread; the most compressed thread commented on today has 6 acronyms.

[Thread #910 for this sub, first seen 8th Aug 2024, 09:05] [FAQ] [Full list] [Contact] [Source code]

[–] [email protected] 13 points 3 months ago

Thank god. Now iOS will finally recognize it

[–] [email protected] 12 points 3 months ago

Next up!

ICANN approves use of .awesome-selfhosted domain for your network

[–] [email protected] 10 points 3 months ago

I guess no one offered anything for .internal

load more comments
view more: next ›