It would have been nice if they came up with something shorter like .lan.
Oh, that's LAN - I thought you'd put ian and I was trying to get the joke. Stupid sans-serif fonts.
Use it anyway.
You go to networking jail for that.
Shit, let's hope the ICANN cops don't find me out then... I've been using it for years!
"I hereby sentence you to two years on your own VLAN with no gateway"
Sorry. I chose .local and I'm sticking to it.
I was using .local, but it ran into too many conflicts with an mDNS service I host and vice versa. I switched to .lan, but I'm certainly not going to switch to .internal unless another conflict surfaces.
I've also developed a host-monitoring solution that uses mDNS, so I'm not about to break my own software. 😅
It's also second only to .com in terms of query volume in ICANN's Magnitude statistics with 980 mil vs .internal's 60 mil. Not sure if that makes it a de facto standard, but it's close.
It should be reserved for sex toys.
Just saying.
I used to wonder why porn sites aren't required to use '.cum' instead of '.com'...
Browsers barf at non https now. What are we supposed to do about certificates?
If you mean properly signed certificates (as opposed to self-signed) you'll need a domain name, and you'll need your LAN DNS server to resolve a made-up subdomain like lan.domain.com. With that you can get a wildcard Let's Encrypt certificate for *.lan.domain.com and all your https://whatever.lan.domain.com URLs will work normally in any browser (for as long as you're on the LAN).
Right, main point of my comment is that .internal is harder to use that it immediately sounds. I don't even know how to install a new CA root into Android Firefox. Maybe there is a way to do it, but it is pretty limited compared to the desktop version.
Nothing, this is not about that.
This change gives you the guarantee that .internal domains will never be registered officially, so you can use them without the risk of your stuff breaking should ICANN ever decide to make whatever TLD you're using an official TLD.
That scenario has happened in the past, for example for users of FR!TZBox routers which use fritz.box. .box became available for purchase and someone bought fritz.box, which broke browser UIs. This could've even been used maliciously, but thankfully it wasn't.
Either ignore like I do or add a self signed cert to trusted root and use that for your services. Will work fine unless you're letting external folks access your self hosted stuff.
Quite literally my first thought. Great, but I can't issue certs against that.
One of the major reasons I have a domain name is so that I can issue certs that just work against any and all devices. For resources on my network. Home or work, some thing.
To folks recommending a private CA, that's a quick way to some serious frustration. For some arguably good reasons. On some devices I could easily add a CA to, others are annoying or downright bullshit, and yet others are pretty much impossible. Then that last set that's the most persnickety, guests, where it'd be downright rude!
Being able to issue public certs is easily is great! I don't use .local much because if it's worth naming, it's worth securing.
Why do I care what ICANN says I can do on my own network? It's my network, I do what I want.
Try using .com for your internal network and watch the problems arise. Their choice to reserve .internal helps people avoid fqdn collisions.
Certain domain names are locally routed only. So if you use internal or local as a tld, you can just assign whatever names you want and your computer won't go looking out on the internet for them. This means you and I can both have fileserver.local as an address on our respective network without conflicting. It's the URI equivalent of 192.168.0.0/16.
YouCANN do anything you want?
I will stick with .lan
But what if your name is not Ian...
Then change it Ian!
Took long enough
Thanks but I hardly needed anyone permission to not use that. .local still works just fine.
Except when it doesn't. It can have issues around multicast dns.
I've had issues with .local on my Android device. Straight up doesn't work. I had to change to .lan
Interesting. I've been using ".home.arpa" for a while now, since that's one of the other often used ways.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| CA | (SSL) Certificate Authority |
| DNS | Domain Name Service/System |
| HTTP | Hypertext Transfer Protocol, the Web |
| HTTPS | HTTP over SSL |
| IP | Internet Protocol |
| SSL | Secure Sockets Layer, for transparent encryption |
| TLS | Transport Layer Security, supersedes SSL |
| VPN | Virtual Private Network |
6 acronyms in this thread; the most compressed thread commented on today has 6 acronyms.
[Thread #910 for this sub, first seen 8th Aug 2024, 09:05] [FAQ] [Full list] [Contact] [Source code]
Missed the opportunity for .myshit.
Thank god. Now iOS will finally recognize it
Next up!
ICANN approves use of .awesome-selfhosted domain for your network
Woohoo! We internal now! No more FQDN collisions!
I guess no one offered anything for .internal
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:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!