146
ICANN proposes creating .INTERNAL domain
(www.theregister.com)
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 31 Jan 2024
146 points (98.0% liked)
Selfhosted
61901 readers
782 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.
-
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!
founded 3 years ago
MODERATORS
A good move!
I’m surprised they didn’t codify “.lan” though since that one is so prevalent.
It's used in many cases where the machine may not be on the LAN and LAN is a technical term. "Internal" is not and to me signifies that it's "not public" aswell as probably managed by someone, well, internally at the entity you're with.
I think needing a VPN to access the internal network is a good practice. And if you're going to be used a VPN anyway, I don't see why you wouldn't use a "fake" TLD like .lan for internal stuff, after all it's just simple DNS rules.