3 ms·

> I don't know why people thought they could start using random TLD's on their own, there was always the risk they could be delegated officially. For a long ti

by cesarb 9y ago

> I don't know why people thought they could start using random TLD's on their own, there was always the risk they could be delegated officially. For a long time, the set of non-country TLDs was mostly static, and country TLDs were always exactly two characters. The risk was always there, but it looked like it was only a theoretical risk, until recently the floodgates opened and nearly every TLD became fair game.

snuxoll 9y ago
People still use .local in this day and age, I’m so freaking tired of editing my avahi-daemon config to not spend 10 seconds resolving internal resources.
- hobarrera 9y ago
  Using .local is just asking for trouble -- avahi/bonjour/mdns have used that pseudo-TLD for ages. Using that locally is a great recipe for things breaking.
  - schoen 9y ago
    In fact, Apple officially registered it for this purpose in order to avoid this kind of conflict. These conflicts with manually-assigned .local names were already happening since the beginning of Apple's zeroconf work, and other people were frustrated with them (you can see on Wikipedia that Microsoft had previously advocated manual use of .local in its documentation). But the designation has been official since 2013. Edit: This was all described in another part of this thread already, sorry for the pure duplication.
CydeWeys 9y ago
"Recently" being relative of course. The big gTLD expansion was first announced in 2008 when the application process for new gTLDs started being worked on. There's been plenty of time to fix things, but as usual, people will delay and only fix things when they break. Hence ICANN's Controlled Interruption process.
- JdeBP 9y ago
  Those of us who used augmented DNS roots knew of this problem long before 2008. In the various augmented root systems, there were a lot more non-country top-level domains a lot (i.e. years) earlier, and people had already registered ones that conflicted with private-use top-level domains beloved of wrongheaded system administrators and developers. AlterNIC had corp., for example. So "recently" is even more relative than that. (-:

by cesarb 9y ago

snuxoll 9y ago

People still use .local in this day and age, I’m so freaking tired of editing my avahi-daemon config to not spend 10 seconds resolving internal resources.

hobarrera 9y ago
Using .local is just asking for trouble -- avahi/bonjour/mdns have used that pseudo-TLD for ages. Using that locally is a great recipe for things breaking.
- schoen 9y ago
  In fact, Apple officially registered it for this purpose in order to avoid this kind of conflict. These conflicts with manually-assigned .local names were already happening since the beginning of Apple's zeroconf work, and other people were frustrated with them (you can see on Wikipedia that Microsoft had previously advocated manual use of .local in its documentation). But the designation has been official since 2013. Edit: This was all described in another part of this thread already, sorry for the pure duplication.

CydeWeys 9y ago

"Recently" being relative of course. The big gTLD expansion was first announced in 2008 when the application process for new gTLDs started being worked on. There's been plenty of time to fix things, but as usual, people will delay and only fix things when they break. Hence ICANN's Controlled Interruption process.

JdeBP 9y ago
Those of us who used augmented DNS roots knew of this problem long before 2008. In the various augmented root systems, there were a lot more non-country top-level domains a lot (i.e. years) earlier, and people had already registered ones that conflicted with private-use top-level domains beloved of wrongheaded system administrators and developers. AlterNIC had corp., for example. So "recently" is even more relative than that. (-: