this post was submitted on 10 Jul 2023
40 points (97.6% liked)

Selfhosted

40173 readers
648 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
 

There are many DNS names options. Which one do you use?

you are viewing a single comment's thread
view the rest of the comments
[–] distantorigin@kbin.cafe 2 points 1 year ago (1 children)
[–] Cerothen@lemmy.ca 2 points 1 year ago (1 children)

I also use .lan I used to use .local for years until I started to have conflict issues with .local resolution on Android when they started using mdns

[–] distantorigin@kbin.cafe 2 points 1 year ago

I didn't care about any of this (my off the shelf Router used .local) and then I started selfhosting more and using pFsense as a router OS. It defaulted to using home.arpa, which was so objectionable that I spent time looking into RFC 6762 and promptly reverted to .lan forever.

The official choices were: .intranet, .internal, .home, .lan, .corp, and .private. LAN was the shortest and most applicable. Choice made.