2 ms·

> In what way is the global namespace being "polluted"? There was a time you could name your hosts server1.dev and server1.prod. These days, what am I supposed

by labawi 7y ago

> In what way is the global namespace being "polluted"? There was a time you could name your hosts server1.dev and server1.prod. These days, what am I supposed to use for internal server communication, lest it some day resolve to something on the internet or a trusted CA creates a valid certificate for it? Domain names were organized in a relatively stable hierarchy, with a set of registries. The way TLD registrations are going, all organizations will want their TLD and we will end up with a single centralized tree of unnumerable registries. You use to know what were the locally relevant domains. Now, is it <company>.co.ccTLD, <company>.ccTLD, or is it <company>.dev, or <company>.<company> or is it <company>.uno, ..gmbh, ..kaufen, ..kinder, or maybe <company>.wazoo, because why not? You get a link to or email from <your-ISP>.talk - is it legit, or a fake in a spamhaus registrar? If you have a .bank, a .cafe, maybe a .shop, but you also do .trade, and .trading, and of course everyone wants to be .top ... of the hundreds of TLDs, are you supposed to register all that could apply and pay large sums for it, because people are going to type <company>.<whatever-i-think-it-is>? If we create dozens(?) of new TLDs per year, noone will remember the difference between TLDs run by nigerian scammers and those run by respectable businesses.

CydeWeys 7y ago
There never has been such a time. It has always been a mistake to use a fake domain name, even just on internal networks. This has caused problems as far back as the 90s, e.g. when companies merged and suddenly realized they had conflicting fake domain names upon connecting their networks and now lots of stuff started failing. For more information see: https://jdebp.eu/FGA/dns-use-domain-names-that-you-own.html https://jdebp.eu/FGA/dns-use-domain-names-that-you-own.html So the only time it has ever been safe to name your hosts server1.dev is within the past year, now that .dev is actually live and you can use a real globally unique domain name that you actually own, thus preventing any of the possible issues that have been there all along. And there aren't any TLDs run by Nigerian scammers. You may be underestimating the difficulty, cost, and technical know how of acquiring and running a TLD.
- labawi 7y ago
  I'm sure ICANN would love to claim ownership of the entire name hierarchy, but I disagree. At least on my servers. First problem with your suggestion - you don't own domains, you rent them. That can change, you have to pay, someone can forget to renew, etc. Though I agree, sometimes it is better to use proper registered domains. When setting up limited scale server-to-server communication I really do not want to interact with DNS. It's all downside and no upside. Servers get names in a subdomain of a widely squatted invalid TLD, names with locally appropriate IPs go in a hosts file and I can be reasonably sure they get resolved to the proper IPs, or as a failure mode - none at all. With the occasional network layer security, it is important to get the IPs right. If the need should arise, I can change the domain. I don't see how using a proper DNS name would be better instead of a clearly local one I can trust.

by labawi 7y ago

CydeWeys 7y ago

There never has been such a time. It has always been a mistake to use a fake domain name, even just on internal networks. This has caused problems as far back as the 90s, e.g. when companies merged and suddenly realized they had conflicting fake domain names upon connecting their networks and now lots of stuff started failing. For more information see: https://jdebp.eu/FGA/dns-use-domain-names-that-you-own.html https://jdebp.eu/FGA/dns-use-domain-names-that-you-own.html So the only time it has ever been safe to name your hosts server1.dev is within the past year, now that .dev is actually live and you can use a real globally unique domain name that you actually own, thus preventing any of the possible issues that have been there all along. And there aren't any TLDs run by Nigerian scammers. You may be underestimating the difficulty, cost, and technical know how of acquiring and running a TLD.

labawi 7y ago
I'm sure ICANN would love to claim ownership of the entire name hierarchy, but I disagree. At least on my servers. First problem with your suggestion - you don't own domains, you rent them. That can change, you have to pay, someone can forget to renew, etc. Though I agree, sometimes it is better to use proper registered domains. When setting up limited scale server-to-server communication I really do not want to interact with DNS. It's all downside and no upside. Servers get names in a subdomain of a widely squatted invalid TLD, names with locally appropriate IPs go in a hosts file and I can be reasonably sure they get resolved to the proper IPs, or as a failure mode - none at all. With the occasional network layer security, it is important to get the IPs right. If the need should arise, I can change the domain. I don't see how using a proper DNS name would be better instead of a clearly local one I can trust.