this post was submitted on 10 Jul 2023
5 points (100.0% liked)

Selfhosted

39964 readers
339 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
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
HybridSarcasm@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
5
What hostname do you use for server? home.box or home.local? (lemmy.world)
submitted 1 year ago by zephyr@lemmy.world to c/selfhosted@lemmy.world
31 comments fedilink hide all child comments
 

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
[–] redcalcium@c.calciumlabs.com 2 points 1 year ago* (last edited 1 year ago) (3 children)

According to IETF, you should only use .intranet, .internal, .private, .corp, .home or .lan for your private network ( RFC 6762 Appendix G ). Using other TLDs might cause issues in the future, especially since new gTLDs seems to show up every few months or so, which can collide with the TLD you use for your local network.

[–] dpflug@hachyderm.io 2 points 1 year ago (2 children)

@redcalcium
Really? Not .local? Why is it the default on so much?
@zephyr

[–] zorflieg@lemmy.world 3 points 1 year ago

A long time ago Microsoft and some teaching sources used .local in example documentation for local domains and it stuck. Like contoso.com was Microsoft's example company. I was taught to use .local decades ago and it took a very long time to unlearn it.

[–] vegetaaaaaaa@lemmy.world 1 points 1 year ago* (last edited 1 year ago) (2 children)

A problem with the .lan TLD (maybe others from this list) is that web browsers do not consider it a TLD when you type it in the address bar, and only show you the option to search for that term in your default search engine. You have to explicitly type https:// before it, to have the option to visit the URL.

E.g type example.com in the address bar -> pressing Enter triggers going to https://example.com. Type example.lan -> pressing Enter triggers a search for example.lan using your default search engine.

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

Little known trick--or perhaps everyone knows it and is quietly laughing behind my back--with Chromium browsers and Firefox (and maybe Safari, I'm not sure), you can add a slash to the end of an address and it will bypass the search.

So, for example, my router on the LAN goes by the hostname "pfsense". I can then type pfsense.lan/ into my address bar and it will bring me to the web UI, no HTTP/s needed.

[–] MangoPenguin@lemmy.blahaj.zone 2 points 1 year ago

You can throw a / after to force it to recognize as a URL too.

[–] erre@feddit.win 1 points 1 year ago (1 children)

The one reserved for residential usage is home.arpa.

https://www.rfc-editor.org/rfc/rfc8375.html

[–] redcalcium@c.calciumlabs.com 1 points 1 year ago* (last edited 1 year ago)

Interesting, so this is the latest recommendation? Which is probably why I haven't seen it in the wild yet, at least in my circles.

Which means they probably going to ~~cash out~~ release gTLDs for .intranet, .internal, .private, .corp, .home and .lan soon...