DNS |
Sponsored by |
This month, ICANN is driving hard to get two of its horses to the finish line. The first is barely a year old - it's the first formal review of ICANN's accountability and transparency. The second horse is going on 4 years old: ICANN's plan to introduce hundreds of new top-level domains (TLDs) for the Internet. Just as these horses have entered the home stretch, one of the racecourse officials is vigorously waving the yellow caution flag. And ICANN would do well to pull back on the reins.
As many of us in the Internet community gear up for the ICANN meeting in Colombia next week, it's important to remember that not everybody embraces the multi-stakeholder approach that we've gradually learned to love. Just a month ago, a group with a very different vision of how to run things wrapped up their own Internet governance meeting in Latin America. Their meeting was three times as long and accomplished about a third as much, but they'd still like to see their model replace the ICANN model.
Bulgaria has proposed for an Internationalized Domain Name (IDN) ccTLD string .?? (Cyrillic for .bg, or U+0431 U+0433), but the proposal was turned down by the ICANN DNS Stability panel in May 2010 without any arguments or an option for appeal. The proposed string is composed of two characters...
In the midst of "Cyber Monday", the day traditionally seen as one of the year's busiest days for online shopping, it is only appropriate to examine the importance DNS plays for online economies. With DNS being at the heart of Internet connectivity it is easy to understand why DNS is important to the growing health of economies whose online health in dollars and euros rest in the billions.
All effective spam filters use DNS blacklists or blocklists, known as DNSBLs. They provide an efficient way to publish sets of IP addresses from which the publisher recommends that mail systems not accept mail. A well run DNSBL can be very effective; the Spamhaus lists typically catch upwards of 80% of incoming spam with a very low error rate. DNSBLs take advantage of the existing DNS infrastructure to do fast, efficient lookups. A DNS lookup typically goes through three computers...
History is a great teacher, we are told. So, on the cusp of an explosion in new top-level domains, what can we learn from the two previous expansions of the Internet's naming space? And what are the pitfalls to avoid? Let's just assume the fundamental and obvious lessons of realistic expectations, a solid business plan and prudent resource management, and instead focus on the little talked about but still critical lessons that will separate the winners and the losers in this race. But first - a caveat!
You wake up, make coffee, sit down by the computer and start reading your favorite web sites. You fire up your favorite browser and type 'www.site.com' on the address bar, hit enter and continue sipping on that coffee. You wait for the page to load, sipping some more coffee - a few seconds later you get the Google search results for 'www.site.com'. You scratch your head, sip some more coffee, and start wondering if you did a typo, but no it is correct - Google is not correcting your spelling.
This visual depicts about half of the currently approved internationalized domain names (IDNs), positioned over their respective regions. Notice the wide range of scripts over India and the wide range of Arabic domains. I left off the Latin country code equivalents (in, cn, th, sa, etc.) to illustrate what the Internet is going to look like (at a very high level) in the years ahead.
November 11, 2010, marked the day when the new Internationalized Domain Name (IDN) contry code Top-Level Domain (ccTLD) .?? (Cyrillic for ?????????? ?????????, Russian Federation) was opened for general registration. Prior to that date the registration was open only for trademark owners and governmental institutions. ... It turned out they needed less than three hours to reach to the 100,000 domain names! Such a gold rush was not expected, and numbers continued to grow - 200,000 within 6 hours... more than 460,000 by today.
What is so secret about the word, "Capacity"? As I read and talk with people I realize the word, "capacity" is typically missing from the DNS discussion. "Capacity" and "Security" are the two cornerstones to maximizing DNS resilience; both of which are typically missing from the DNS discussion. Have you seen a single DNS node easily process over 863,000 queries per second? Have you seen a network routinely handle over 50Gbits/second in outbound traffic alone without breaking a sweat?