this post was submitted on 08 Aug 2024
498 points (99.0% liked)

Selfhosted

40347 readers
347 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
[–] r00ty@kbin.life 104 points 3 months ago (6 children)

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

[–] EnderMB@lemmy.world 56 points 3 months ago (2 children)

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

[–] Boomkop3@reddthat.com 9 points 3 months ago
[–] corsicanguppy@lemmy.ca 6 points 3 months ago (1 children)
[–] acockworkorange@mander.xyz 4 points 3 months ago

I don’t get it.

[–] xcjs@programming.dev 29 points 3 months ago (2 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. 😅

[–] possiblylinux127@lemmy.zip 18 points 3 months ago (1 children)

.internal takes to long to type

[–] xcjs@programming.dev 10 points 3 months ago

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

[–] r00ty@kbin.life 3 points 3 months ago (1 children)

Yeah, I don't really have a use at home for mDNS. None that I can think of, anyway. Pretty sure I was using it before MDNS was a thing.

[–] Supermariofan67@programming.dev 5 points 3 months ago (1 children)

Accessing printers? Resolving hostnames of internal hosts? I can't imagine having a lan without mDNS

[–] r00ty@kbin.life 2 points 3 months ago

Oh. Internal hosts, I just setup on my own DNS.. No need for that. Printer, can't say I've ever had a problem.

[–] chrisbit@leminal.space 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.

[–] justme@lemmy.dbzer0.com 21 points 3 months ago (1 children)

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

[–] anytimesoon 7 points 3 months ago (1 children)

I'm using .home and have not had any issues. Would you mind sharing what problems you've come across so I know what to expect?

[–] ayyy@sh.itjust.works 3 points 3 months ago

The main problem I have is waking up in the middle of the night worrying that ICANN pulled some more stupid corrupt bullshit that only makes networking worse and breaks my config.

Just look elsewhere in this thread: someone thinks that using .honk as a joke is safe. But what about .horse? .baby? .barefoot? .cool? (I stopped scrolling through the list at this point but you can see how arbitrary and idiotic things have become.)

[–] dhtseany@lemmy.ml 8 points 3 months ago (5 children)

I still haven't heard a convincing argument to not use .local and I see no reason to stop.

[–] SirEDCaLot@lemmy.today 46 points 3 months ago (1 children)

Mainly conflicts with mDNS. However it's shitty IMHO that the mDNS spec snarfed a domain already in widespread use, should have used .mDNS or similar.

[–] xcjs@programming.dev 8 points 3 months ago

That I agree with. Microsoft drafted the recommendation to use it for local networks, and Apple ignored it or co-opted it for mDNS.

[–] KingThrillgore@lemmy.ml 26 points 3 months ago (1 children)

.local is already used by mDNS/Zeroconf.

[–] x00z@lemmy.world 10 points 3 months ago

You mean mDNS/Zeroconf are using a tld that was already being used.

[–] corsicanguppy@lemmy.ca 6 points 3 months ago (3 children)

Tell me you don't share a net with Macs without using those words.

[–] xcjs@programming.dev 4 points 3 months ago

Macs aren't the only thing that use mDNS, either. I have a host monitoring solution that I wrote that uses it.

[–] ChapulinColorado@lemmy.world 2 points 3 months ago

Even on windows sometimes depending on the target host, I’ve had to type host.local. (Final dot to do exact match) instead of host.local

This didn’t seem to affect other domains. I’m assuming it was due to special handling of .local

[–] ayyy@sh.itjust.works 1 points 3 months ago

mDNS hasn’t been a just-Apple thing for decades. Do you still call it Ren-dess-voos like the Gaston character in Beauty and the Beast?

[–] ShortFuse@lemmy.world 4 points 3 months ago* (last edited 3 months ago)

I've also used .local but .local could imply a local neighborhood. The word itself is based on "location". Maybe a campus could be .local but the smaller networks would be .internal

Or, maybe they want to not confuse it with link-local or unique local addresses. Though, maybe all .internal networks should be using local (private) addresses?

[–] billwashere@lemmy.world 1 points 3 months ago

My main issue was it doesn’t play well with Macs.

[–] UberMentch@lemmy.world 5 points 3 months ago (1 children)

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

[–] r00ty@kbin.life 1 points 3 months ago

Hmm, the only issue I had was because it was using the DoH (which I don't have a local server for). Once I disabled that, it was fine.