4 ms·

Something I haven't seen discussed: how are web browsers going to handle somebody typing a generic keyword that is also TLD into the address bar? The chrome-sty

by necubi 14y ago

Something I haven't seen discussed: how are web browsers going to handle somebody typing a generic keyword that is also TLD into the address bar? The chrome-style omnibar that every browser has since adopted is predicated on the fact that URLs are fairly easily recognizable. But if amazon owns "books" and hosts something at http://books/ 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.]

garethadams 14y ago
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./ http://to./ However, it hasn't been available for a long time now. EDIT: As pointed out below, http://ac/ http://ac/ points to a real website
- Alexandervn 14y ago
  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/ http://ac/ through it's IP-address in the A-record (http://193.223.78.210/ http://193.223.78.210/).
- justincormack 14y ago
  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-July/004155.html https://lists.dns-oarc.net/pipermail/dns-operations/2009-Jul...
Sami_Lehtinen 14y ago
With Firefox .ac doesn't work but ac. does. So when you access .books you might need to write books.
rootzoned 14y ago
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?

by necubi 14y ago

garethadams 14y ago

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./ http://to./ However, it hasn't been available for a long time now. EDIT: As pointed out below, http://ac/ http://ac/ points to a real website

Alexandervn 14y ago
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/ http://ac/ through it's IP-address in the A-record (http://193.223.78.210/ http://193.223.78.210/).
justincormack 14y ago
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-July/004155.html https://lists.dns-oarc.net/pipermail/dns-operations/2009-Jul...

Sami_Lehtinen 14y ago

With Firefox .ac doesn't work but ac. does. So when you access .books you might need to write books.

rootzoned 14y ago

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?