Comment on ICANN proposes creating .INTERNAL domain
Corngood@lemmy.ml 11 months ago
Huh, I’ve seen .local used for this quite a bit and only just now realised that it’s meant for something else.
I’ve also seen .corp 🤮
Comment on ICANN proposes creating .INTERNAL domain
Corngood@lemmy.ml 11 months ago
Huh, I’ve seen .local used for this quite a bit and only just now realised that it’s meant for something else.
I’ve also seen .corp 🤮
perishthethought@lemm.ee 11 months ago
And .home.
Hopefully this .Internal domain takes off and becomes generally recognized as the only correct non-routable domain we all use. Otherwise it’s just the latest addition to the list of possible TLDs and confusion continues.
foggy@lemmy.world 11 months ago
I’m just waiting for .exe
EddyBot@feddit.de 11 months ago
.zip is already a thing
www.malwarebytes.com/blog/news/2023/05/…/amp
AceFuzzLord@lemm.ee 11 months ago
That one is absolutely abhorrent because I know as a fact my parents would easily fall for a .zip domain leading to a virus infested site thinking it’s actually them getting a zip file because they don’t know better. At least the first few times they’d fall for it.
Bitrot@lemmy.sdf.org 11 months ago
It’s such a shitty situation. ICANN is not going to sell .home or .corp as they found a crapton of traffic when they checked for it, but IETF never finished an RFC for them - however people easily stumble into the draft RFC that lists what they were thinking of, and assume stuff like .lan is good to go too. They’re only safe by policy, but unsanctioned.
.home.arpa is safe, per RFC, but user unfriendly to normal people. There are a few others but none a corporation would realistically use. I’ve used . internal for lab testing stuff for ages, so this is extra good news for me I guess.
Really I wish they’d have just reserved the most common ones rather than getting caught in some bureaucratic black hole.