SoylentNews is people
SoylentNews
Anyone still reeling after Google snagged .dev for their own nefarious purposes will be relieved to learn that Internet Corporation for Assigned Names and Numbers (ICANN) has decided (after 6 years) to reject the applications for .home, .corp, and .mail.
Twenty companies paid the $185,000 application fee to ICANN back in 2012 to oversee the top level domains.
Seventeen months later an ICANN commissioned report noted that .home, and .corp were by far the most frequently queried top level domains and argued that they should not be added to the public internet. Eleven months later they were formally designated as "high risk" extensions.
Further study, as well as a failed attempt by the Internet Engineering Task Force (IETF) to add the 3 to the official list banned from the internet took another 15 months.
Finally in late 2017, 15 months after prompting from the original applicants, they revisited the issue again and decided to reject the applications - and in the interest of fairness, fully refund the application fees.
So there you have it, you can now use .home, .corp, and .mail on your internal networks.
More info at The Register:
https://www.theregister.co.uk/2018/02/12/icann_corp_home_mail_gtlds/
ICANN meeting minutes:
https://www.icann.org/resources/board-material/resolutions-2018-02-04-en#2.c
(Score: 2) by maxwell demon on Sunday February 18 2018, @07:32PM (1 child)
You have to rewrite everything referring to those local addresses. Documentation. Links in internal documents. Addresses in configuration files. Addresses hard-coded into applications (are you absolutely sure that nobody did this for any internal application?). Are you sure that list is exhaustive?
The Tao of math: The numbers you can count are not the real numbers.
(Score: 2) by fyngyrz on Sunday February 18 2018, @11:09PM
So, what you're really saying is your IT is chaotic, out of your control, and that is why you can't move the network around.
Fair enough. So the thing is, my LAN and the applications that work with it are not out of my control, so I don't have to deal with such things. All network references are via common configuration files, including my documentation, just as they should be, so it's zero problem to change this sort of thing. It was designed that way. By me. And I'm not running network-aware OPC* that can screw me (really that's a matter of security, but not having to worry about embedded rogue network configurations is a definite side benefit.)
If you're running apps you don't have control of on your network I can certainly see how that would cause you serious problems. Of many kinds. I tend to forget that the general run of IT out there is best described as "a chaotic mess." I'm definitely spoiled by having encountered, and solved, these problems years ago, and by forbidding network-aware OPC to run there.
So I'll put it this way, then: I can make such changes within the LAN with very minor effort when that needs to happen, or I simply want it to. So this kind of decision by WAN TLD decision-makers is of no significant consequence at all to me.
YMMV. But... you'd be considerably better off if it didn't. :)
--------------------------------------------------------------
*OPC - Other People's Code