If a company has its own internal network with its own DNS, does it still need to conform to ICANN's name assignments? I thought it doesn't...?
If a company has its own internal network with its own DNS, does it still need to conform to ICANN's name assignments? I thought it doesn't...?
Except (correct me if I'm wrong), this is not a "modified network", it can be another disconnected network that's just as "correct" in the standard conformance aspect as the Internet. It's more like Chrome is "modified" to support one network better than others - or rather, to possibly break on other networks.
In fact, it seems to me like the very idea of HSTS preload list isn't friendly with UAs working on multiple separate networks.
But yeah, you're right that this is what they are designed for after all. (I'm also probably slightly biased, since some of our test environments use .dev domain in our LAN.)
First, you will begin leaking internal data by means of DNS requests, server connections, maybe even internal emails - e.g. when a client attempts to connect to the intranet outside of VPN.
Second, you obviously won't be able to communicate with the new owners of that domain.
Probably better to just use real globally delegated domain names though.
ICANN can't keep names unique if people just take them.