.localhost is already reserved for the loopback, per RFC 2606, but I agree with you in general. A small network shouldn’t have to have a $10-15/year fee to be compliant if they don’t want to use a domain outside their network.
As other posters have mentioned, .lan .home .corp and such are so widely used that ICANN can’t even sell them without causing a technical nightmare.
Yes, you’re right, RFC 6762 proposes reserving .local for mDNS. I was not aware of this until you brought it up, hence the dangers of using using TLDs not specifically designated for internal use.
Very few as this ruling would reserve .internal for local DNS only and forbid it at the global level. This is ICANN’s solution to people picking random .lan .local .internal for internal uses. You’ll be able to safely use .internal and it will never resolve to an address outside your network.
Yeah, that’s why they want change.
Considering how thick that ice is and how fast it’s moving, this is actually pretty terrifying.
It’s really cool to see in real time an example of how a glacier can erode the terrain though.
We just got vertical align last month. There’s so many things they should be working on but are too busy trying to add more ads or monetization features.
I think the web is just too long in the tooth at this point but there’s nothing we can do.