39
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 10 Jul 2023
39 points (97.6% liked)
Selfhosted
39683 readers
540 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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
According to IETF, you should only use
.intranet,.internal,.private,.corp,.homeor.lanfor 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.The one reserved for residential usage is
home.arpa.https://www.rfc-editor.org/rfc/rfc8375.html
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,.homeand.lansoon...A problem with the
.lanTLD (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 typehttps://before it, to have the option to visit the URL.E.g type
example.comin the address bar -> pressing Enter triggers going tohttps://example.com. Typeexample.lan-> pressing Enter triggers a search forexample.lanusing your default search engine.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.
You can throw a
/after to force it to recognize as a URL too.@redcalcium
Really? Not .local? Why is it the default on so much?
@zephyr
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.
@dpflug @redcalcium @zephyr it is reserved for mDNS.
@sifrmoja
Ah, yep. Now that you say it. Thanks for cluing me in.
@redcalcium @zephyr
I can vouch for the fact that .local stopped working suddenly in most browsers a year or two ago, I was forced to migrate to .internal