Re:I bought netflix.soy
by moonchild on Monday May 25, 2020 @06:15PM
(#23305513)
http://cm./ used to resolve
[ Parent
| on HN ]
https://news.ycombinator.com/item?id=974111
http://to./ used to be a URL shortener.
Either the rules on ccTLDs are different, or it's a recentish crackdown.
There are no rules for ccTLDs, which their countries like to claim as sovereign property (see https://meetings.icann.org/en/dublin54/schedule/wed-ccnso-me... and https://gac.icann.org/principles-and-guidelines/public/princ... for some of the views)
Some ccTLDS voluntarily agree to abide by the same rules and operational requirements as the gTLDs - https://www.icann.org/resources/pages/cctld-2012-02-25-en has more details.
This means, for example, than ccTLDs aren’t bound by the findings from SAC053 at https://www.icann.org/en/system/files/files/sac-053-en.pdf which have been included in the gTLD contracts.
Wow, that's a glimpse into the past
.cm is a ccTLD, not a gTLD. All two-letter TLDs are ccTLDs and all 3+ letter TLDs are gTLDs. Countries have wide latitude to do whatever they want with their ccTLDs.
http://ai./ still works
What happens if I have a computer on my network named ai? Wouldn't it cause a conflict?
I called my FreeNAS box freenas because I didn't feel very creative, and I can browse to it as http://freenas or http://freenas./ but if they took a domain of 'freenas' suddenly that means I have to do extra work and rename my stuff. Doesn't seem fair!
You should have used a reserved TLD like `.local'. If you set it as the local domain name `ai' and `ai.local' would work. `ai.' would not work, as the dot at the end tells it to look at the top level. (like the slash at the beginning of an absolute path)