Home / Blogs

Domain Names Without Dots

Now that ICANN has approved a potentially vast expansion in the number of generic Top-Level Domains, there’s considerable interest in and confusion about how these names can be used. For example if someone registers “dot BRAND”, can they advertise http://brand/ and have it work?

No!

No! Or at least, mostly not. Because on most laptops, desktops, and mobile platforms, the operating system will try that name under the local domain before trying it as a global name. This behaviour comes from a time when domain names were first used to identify Internet resources and not yet as a way to reach Web assets. Many if not most web browsing platforms have a DNS search list that they’ll use to find out if a name that looks local (having no dots in it) is in fact local.

Search Lists

On my desktop system here at “six.vix.com” the default search list has just “vix.com” but since I often access Internet resources belonging to my employer (ISC) I have also added “isc.org” to my search list. If I enter http://brand/ into my web browser it will search first for “brand.vix.com” and then “brand.isc.org” and if either of those names exists then my browser will assume that this is what I want and will take me there. Only if there is no “brand” available in my DNS search list will it find the “dot BRAND” registration in the root zone.

Relief?

If we began right now in the Internet Engineering Task Force (IETF) working on a new Request For Comments (RFC) document that discommends this DNS “search list” behaviour, and if IETF could reach consensus on the matter in an uncharacteristically short time (let’s say within a year) then the global installed base of web browsers could be expected to mostly adopt this new behaviour within one decade. In other words there’s a very long tail on the installed base even in this mobile-dominated gadget market we all mostly use. Expecting “dot BRAND” to work as a naked URL would be at best unrealistic.

Just as important, the Internet is larger and older than the Web, and other Internet systems such as E-mail will mostly not accept naked top level names at all. As an example, e-mail to “person@brand” will probably not reach the mail servers for “dot BRAND”.

Conclusion

Because of the “land rush” that ICANN’s approval of the new gTLD expansion program is likely to set off, I think it’s important for all applicants (and their investors) to know about this important limitation in how these new gTLD names can be used. Top level domains are expected by most Internet endpoints to be used only for the registration of subdomains (like for example Store.BRAND or Company.BRAND) and it’s my hope that all applicants for new gTLDs will fully understand this before they launch their branding campaign or even before they call their business plan “done”.

By Paul Vixie, VP and Distinguished Engineer, AWS Security

Dr. Paul Vixie is the CEO of Farsight Security. He previously served as President, Chairman and Founder of Internet Systems Consortium (ISC), as President of MAPS, PAIX and MIBH, as CTO of Abovenet/MFN, and on the board of several for-profit and non-profit companies. He served on the ARIN Board of Trustees from 2005 to 2013, and as Chairman in 2008 and 2009. Vixie is a founding member of ICANN Root Server System Advisory Committee (RSSAC) and ICANN Security and Stability Advisory Committee (SSAC).

Visit Page

Filed Under

Comments

Will IPv6 be a factor in this new (g)TLD schema? Richard Donaldson  –  Jun 21, 2011 5:15 PM

While understanding your points on current infrastructure limitations with respect to the new .everything and name resolution, I am wondering if this will trigger yet further expansion of internet infrastructure such that it will concurrently stimulate more IPv6 adoption?  For example, in APNIC region, will this inspire many more entrepreneurs to get their presence online and in turn require more IP space (yes, my bias is in finding the different IPv6 inflection points that are upcoming - virtual and mobile have been identified already, curious as to your thoughts here)

Comment Title:

  Notify me of follow-up comments

We encourage you to post comments and engage in discussions that advance this post through relevant opinion, anecdotes, links and data. If you see a comment that you believe is irrelevant or inappropriate, you can report it using the link at the end of each comment. Views expressed in the comments do not represent those of CircleID. For more information on our comment policy, see Codes of Conduct.

CircleID Newsletter The Weekly Wrap

More and more professionals are choosing to publish critical posts on CircleID from all corners of the Internet industry. If you find it hard to keep up daily, consider subscribing to our weekly digest. We will provide you a convenient summary report once a week sent directly to your inbox. It's a quick and easy read.

Related

Topics

Cybersecurity

Sponsored byVerisign

Threat Intelligence

Sponsored byWhoisXML API

Domain Names

Sponsored byVerisign

New TLDs

Sponsored byRadix

DNS

Sponsored byDNIB.com

Brand Protection

Sponsored byCSC

IPv4 Markets

Sponsored byIPv4.Global