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

Selfhosted

39206 readers
396 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 102 points 1 month ago (27 children)

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

[–] xcjs@programming.dev 29 points 1 month ago (5 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 1 month ago (1 children)

.internal takes to long to type

[–] xcjs@programming.dev 10 points 1 month ago

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

load more comments (3 replies)
load more comments (24 replies)