4 ms·
Eh, .internal is fine, but it's 8 characters to type. I'll probably keep using .lan until someone else takes it.
by p1mrx 3y ago
Eh, .internal is fine, but it's 8 characters to type. I'll probably keep using .lan until someone else takes it.
- ahmedfromtunis 3y agoYou still can provide your input on the matter till march; so it's not too late (yet): https://www.icann.org/en/public-comment/proceeding/proposed-top-level-domain-string-for-private-use-24-01-2024 https://www.icann.org/en/public-comment/proceeding/proposed-...
- p1mrx 3y agoThe problem is that .internal is the bureaucratically correct answer, and not all internal networks are LANs. Maybe they can reserve both .interNAL and its convenient abbreviation, which just happens to be written backwards because it's DNS.
- ChrisArchitect 3y agoHa, excellent
- p1mrx 3y agoSubmitted to ICANN; everybody keep yelling .interNAL until it happens!
- pxtail 3y agoAnswer is simple and straightforward - nothing like this is going to happen because short abbreviations and any potential short alternatives can be sold and sweet sweet money can be extracted
- junon 3y agoNot all use cases for .internal involve a LAN though.
- deng 3y agoWait, so all the '.io' domains are actually registered by people operating in the British Indian Ocean Territory? Seriously, .lan is just a convention. For all I care they could come up with any three-letter thingy, as long as there's a mutual understanding that no global DNS will ever resolve it.
- p1mrx 3y agoPer my other comment, we could define LAN to be the abbreviation for interNAL, because INT was already taken.