Re:Tech press misses Google/Amazon name grab
by garethadams on Friday June 15, 2012 @10:08PM
(#4119657)
Yes. Tonga turned their TLD `.to` into a domain shortener, although because of the browser issue you mention it generally had to be accessed via http://to./
However, it hasn't been available for a long time now.
EDIT: As pointed out below, http://ac/ points to a real website
Re:Tech press misses Google/Amazon name grab
by Alexandervn on Saturday June 16, 2012 @04:31AM
(#4120158)
My DNS provider (also on my VPS) can't resolve both domain names.
I can 'dig' the domain names though and at least visit http://ac/ through it's IP-address in the A-record (http://193.223.78.210/).
Re:Tech press misses Google/Amazon name grab
by justincormack on Saturday June 16, 2012 @04:36AM
(#4120164)
Apparently they are not supposed to exist any more. I think they are not allowed on the new ones but can't find source now.
https://lists.dns-oarc.net/pipermail/dns-operations/2009-Jul...
Re:Tech press misses Google/Amazon name grab
by rootzoned on Saturday June 16, 2012 @07:56PM
(#4121818)
Browser can and sometimes do override DNS. The omnibar is one recent example. This is obviously very bad.
It is like the NXDOMAIN problem.
Is it the web? Or is it some company's interpretation of the web? "In this situation, when the user types ______ the user should be directed to ______."
Remember AOL keywords?
Re:Tech press misses Google/Amazon name grab
by Sami_Lehtinen on Saturday June 16, 2012 @12:51PM
(#4121006)
With Firefox .ac doesn't work but ac. does. So when you access .books you might need to write books.
But if amazon owns "books" and hosts something at http://books/, should browsers navigate to Amazon whenever someone attempts to search for "books"?
[Actually, is it even allowed to host A records directly on a TLD? I've been reading through RFCs and haven't seen it explicitly disallowed, but nobody seems to have done it with a currently-available TLD.]