News for hackers. Stuff that matters.
Re:I bought netflix.soy by tylerhou on Monday May 25, 2020 @05:20PM (#23305112)
Infrastructure changes aren't even needed; Google already owns the .google TLD. All they would need to do is attach an A record to the root.
Re:I bought netflix.soy by three_seagrass on Monday May 25, 2020 @08:44PM (#23306354)
Sure, but why would they?

Can you imagine all the search advertising Google would lose if they allowed just 'nike' and 'att' to resolve the websites in Chrome, rather than search results?

Re:I bought netflix.soy by runawaybottle on Monday May 25, 2020 @11:21PM (#23307104)
Did we just find the secret to beating google?
Re:I bought netflix.soy by CydeWeys on Monday May 25, 2020 @05:56PM (#23305368)
ICANN doesn't allow A records on the DNS root on gTLDs. If they did, we already would've.
Re:I bought netflix.soy by computerfriend on Tuesday May 26, 2020 @01:00AM (#23307574)
This explains so much. I'd always wondered why e.g. CERN's website was served from home.cern instead of just cern.
Re:I bought netflix.soy by moonchild on Monday May 25, 2020 @06:15PM (#23305513)
http://cm./ used to resolve
Re:I bought netflix.soy by Macha on Monday May 25, 2020 @06:50PM (#23305723)
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.

Re:I bought netflix.soy by sleevi on Monday May 25, 2020 @07:20PM (#23305912)
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.

Re:I bought netflix.soy by vpzom on Monday May 25, 2020 @07:48PM (#23306072)
Wow, that's a glimpse into the past
Re:I bought netflix.soy by CydeWeys on Monday May 25, 2020 @07:11PM (#23305850)
.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.
Re:I bought netflix.soy by odensc on Monday May 25, 2020 @09:11PM (#23306492)
http://ai./ still works
Re:I bought netflix.soy by hnick on Tuesday May 26, 2020 @02:16AM (#23307979)
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!

Re:I bought netflix.soy by jtvjan on Tuesday May 26, 2020 @05:55AM (#23309090)
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)
Re:I bought netflix.soy by hnick on Tuesday May 26, 2020 @06:33AM (#23309343)
Ah yes I forgot that, .local does work so I guess that fixes that problem.
Re:I bought netflix.soy by captn3m0 on Monday May 25, 2020 @05:49PM (#23305328)
The used to have an A record on some of the other TLDs they own.

I maintain a list at captnemo.in/tld-a-record

Re:I bought netflix.soy by CydeWeys on Monday May 25, 2020 @07:14PM (#23305869)
Do you remember the details?
Re:I bought netflix.soy by captn3m0 on Wednesday May 27, 2020 @05:18AM (#23321052)
Yes, I did a blog post when it happened: https://captnemo.in/blog/2018/06/02/google-tld-no-more-a-rec....

Google was pointing its TLDs to 127.0.0.53, and once they started using the TLDs actively, they removed the records.