view the rest of the comments
Selfhosted
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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
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!
100% this.
home.arpais the proper way to do this.Unless you have a domain you own, which I do, but still use
home.arpaanyway.Just use .lan
It is way simpler and has been in use long before .home.arpa
Use the RFC defined special use domain https://www.iana.org/assignments/special-use-domain-names
Why though?
It was pushed as a standard after .lan was in use
For the same reason you use RFC provided private IPv4 ranges.
Because there is a standard.
Also, there is nothing stopping
lan.getting registered as a TLD.Except that isn't really a fair comparison. Private ranges aren't any more complicated than public ranges so it doesn't impact me when using IPv4 private IPs.
.home.arpa is one of the most "designed by committee" domains I have heard in my life. It is way longer than .lan and defeats the point of local domains to begin with. I might as well use a public domain instead. .lan was around long before the standard and will be around long after
If .lan becomes a TLD (it won't) I can always go though and change it to something like lan1 or .mylan both of which would be shorter and easier to type