5 ms·
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.
by tylerhou 6y ago
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.
- captn3m0 6y agoThe used to have an A record on some of the other TLDs they own. I maintain a list at captnemo.in/tld-a-record
- CydeWeys 6y agoDo you remember the details?
- captn3m0 6y agoYes, I did a blog post when it happened: https://captnemo.in/blog/2018/06/02/google-tld-no-more-a-records/ 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.
- CydeWeys 6y agoICANN doesn't allow A records on the DNS root on gTLDs. If they did, we already would've.
- moonchild 6y agohttp://cm./ http://cm./ used to resolve
- deleted 6y ago[deleted]
- Macha 6y agohttps://news.ycombinator.com/item?id=974111 https://news.ycombinator.com/item?id=974111 http://to./ http://to./ used to be a URL shortener. Either the rules on ccTLDs are different, or it's a recentish crackdown.
- sleevi 6y agoThere are no rules for ccTLDs, which their countries like to claim as sovereign property (see https://meetings.icann.org/en/dublin54/schedule/wed-ccnso-members/presentation-sovereignty-property-rights-21oct15-en.pdf https://meetings.icann.org/en/dublin54/schedule/wed-ccnso-me... and https://gac.icann.org/principles-and-guidelines/public/principles-cctlds.pdf 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 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 https://www.icann.org/en/system/files/files/sac-053-en.pdf which have been included in the gTLD contracts.
- vpzom 6y agoWow, that's a glimpse into the past
- CydeWeys 6y ago.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.
- odensc 6y agohttp://ai./ http://ai./ still works
- hnick 6y agoWhat 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 http://freenas or http://freenas./ 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!
- deleted 6y ago[deleted]
- jtvjan 6y agoYou 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)
- hnick 6y agoAh yes I forgot that, .local does work so I guess that fixes that problem.
- computerfriend 6y agoThis explains so much. I'd always wondered why e.g. CERN's website was served from home.cern instead of just cern.
- three_seagrass 6y agoSure, 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?
- runawaybottle 6y agoDid we just find the secret to beating google?