4 ms·
> Not doing so is way worse though. You could be leaking all sorts of internal requests to a malicious attacker who does register that domain name. It is, but
by chimeracoder 9y ago
> Not doing so is way worse though. You could be leaking all sorts of internal requests to a malicious attacker who does register that domain name.
It is, but again, it doesn't help that none of the reserved TLDs actually address the primary use case here for a lot of companies. We can both agree that the companies should be registering their private domains, but clearly most aren't, and there's no reason they shouldn't have a free, reserved-for-private use space that does address it.
- JdeBP 9y agoActually, there are at least two reasons, which are in boldface in the Frequently Given Answer that I have already mentioned. * http://jdebp.eu./FGA/dns-use-domain-names-that-you-own.html http://jdebp.eu./FGA/dns-use-domain-names-that-you-own.html
- CydeWeys 9y agoGood points. I'd also say that, while having TLDs for testing usage is acceptable, there should never be any designed for production use as that would seemingly endorse the idea. The best practice (to use domains/subdomains that you own) should always be followed, and just because people do the wrong thing doesn't mean ICANN or the IETF should go out of their way to make the wrong thing easier to do.