Home / Blogs

2008: A Historic Year for DNS

Alexa Raad

As we start the new year, it is worth noting some of the major events and news in 2008 that shaped the industry and fueled considerable discussions. Last year's occurrences made for a very historic year, bearing the seeds of future changes for the DNS and domain name industry.

The "Kaminsky Bug" and DNSSEC

In August Dan Kaminsky unveiled the flaw that leaves a "gaping hole" in the Domain Name System (DNS). The coverage of Kaminsky's bug proved many early advocates and pioneers right. DNSSEC is the best fix and a needed upgrade to the DNS infrastructure.

Much credit belongs to the Swedish country code domain, .SE, the first to implement DNSSEC and to Nominet (the registry for .UK) who championed the need for it before we (the .ORG registry) announced as the first gTLD to start implementation.

What came to be termed as the "Kaminsky bug", changed the debate on DNSSEC from "Do we really need DNSSEC?" to "How do we implement DNSSEC"?

Expansion and introduction of new Top-Level Domains (TLDs)

In June, ICANN announced the process for expansion of new gTLDs. Note that there will most likely be a few gTLDs that make sense by truly serving the end-user need, perhaps via an innovative application. But, user confusion will result from a flood of new gTLDs which serve no discernable purpose. Most internet users will not immediately be aware of new TLDs, and even if and when they become aware, they will not be able to correctly remember the site address. So very likely they will simply defer to the search engine. Browser manufacturers are already figuring this out and are incorporating search function right into the address bar, like Google Chrome undermining the categorization that exists because of the TLDs.

If address bar and search functions are merging and if users increasingly use search engines rather than direct navigation to resolve to a site, how relevant will TLD designations be? Probably far less than today.

And what about the variety and choice the spammers, phishers and distributors of malware will now have in terms of new TLDs to target? This doesn't even begin to touch on the impact on brands and trademark holders who will have to spend even more money protecting their brands and registering them in hundreds of sunrise periods. And lastly, where is the data that in fact the end-user wants upwards of hundreds of new TLDs to help them navigate? On December 18, NTIA posted a comprehensive set of comments to ICANN's proposal which effectively halted the current plan and timetable due to some of these same concerns and lack of research. We believe these comments point out the needed due diligence before moving forward.

Lines between Registries and Registrars starting to fade

ICANN also made public the much anticipated CRAI report. The distinct lines of separation between registries and registrars will blur as a select few registrars will try their hands at the registry business. Bottom-line: we believe ICANN's policy should bar cross ownership of registries and registrars (except in some limited cases for small private TLDs). There are just too many opportunities for anti-competitive behavior if registrars own registries and give their captive registries special treatment. If not, then ICANN should make any new ownership policy equally applicable to registries and registrars.

Industry leaders "stepping up to the plate"

In 2008, we started initiatives such as the DNSSEC Industry Coalition and the Registry Internet Safety Group (RISG) and helped form the Arabic Script IDN Working Group. The credit goes to the members of these groups who have volunteered to work together and donated experts and time to delve into problems that affect each and every Internet user today. The problems range from how to thwart phishing and malware and how to streamline DNSSEC implementation across multiple registries to how to enable Arabic IDNs to work across multiple languages and registries. The end user benefits most of all, and we believe collaboration is the wave of the future in these efforts.

ICANN shuts bad actor registrars

After a few highly publicized episodes of bad actor domain registrars, and much criticism of slow response, ICANN moved to terminate the accreditation of an especially egregious registrar EstDomains effective November 24th. Let's hope the next ones will also be swiftly terminated. Registrars with questionable practices erode customer trust and are bad for everyone's business.

Domain Tasting plunges

In the past few years our industry has experienced something of a boom, not unlike the real estate market, complete with speculation, a robust secondary market and rapid fire growth. 2008 was the year of the recession, initiated ironically enough with the real estate market. The 20% to 30% hyper growth is no more. Was the end to the hypergrowth just due to the recession?

Top two in my mind are the changes in the Google AdSense model as well as the end of domain tasting. PIR (the .ORG registry) was the first registry to enact an Excess Deletion Fee for domain tasting. The net result for us was a much more stable base. But — pardon the pun — the "distaste" for domain tasting spread far enough for ICANN to enact limits on the Add Grace Period (AGP — the source of the problem). These factors most likely led to the slowdown in growth of domain names in 2008.

Governments push for their own Internationalized Domain Names (IDNs)

Push has been coming from governments who want an IDN of their own sooner rather than later. The Internet is the great frontier, and IDNs are certainly valuable when used to enable people to express their names and hence desired addresses as their language and script intended and not as a transliteration of English. The worrisome notion comes when the urgency for IDNs are bound and rolled into highly nationalistic sentiments which more often divide than unite.

GoDaddy is the undisputed market leader among registrars

GoDaddy claims to have registered over 32 million domains. It is no secret that they are a smart and innovative marketing machine. For their competitors, they are a formidable force to beat on the retail game, leaving them to ponder the cost of competing head-on.

Gambling and the Kentucky Domains

A recent law suit in Kentucky has attracted world-wide attention because it could create a very dangerous precedent — the application of local law to the domain name system and Internet web sites that are available globally. Even though the Kentucky case only involves Kentucky gambling laws, the dangerous precedent is that regimes around the world with oppressive local laws restricting speech or religion might attempt similar litigation.

So there you have it, a reflection on the peaks and valleys of the DNS and domain name industry in 2008. I look forward to an amazing 2009 and the interesting and entertaining news to come.

By Alexa Raad, CEO of Architelos Architelos provides consulting and managed services for clients applying for new top-level domains, ranging from new TLD application support to launch and turnkey front-end management of a new TLD. She can be reached directly at araad@architelos.comVisit Page
Follow CircleID on
SHARE THIS POST

If you are pressed for time ...

... this is for you. 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.

I make a point of reading CircleID. There is no getting around the utility of knowing what thoughtful people are thinking and saying about our industry.

Vinton Cerf, Co-designer of the TCP/IP Protocols & the Architecture of the Internet

Share your comments

Alexa: You mention the Kentucky case, and George Kirikos  –  Jan 08, 2009 8:40 PM PST

Alexa: You mention the Kentucky case, and the dangerous precedent it creates. Yet, PIR is adopting an anti-abuse policy that gives itself the same powers as Kentucky has asserted. Where are the safeguards and due process in that anti-abuse policy for innocent registrants who are falsely accused and given the death sentence summarily?

The new PIR policy on dealing with Alexa Raad  –  Jan 09, 2009 8:51 AM PST

The new PIR policy on dealing with abusive domain names has absolutely nothing to do with the Kentucky case involving gambling domains. Kentucky is attempting to enforce its own state law on Internet domains that are global in operation. Under PIR's agreement with ICANN to operate the registry for .ORG, PIR has always had a responsibility, spelled out in its agreement with registrars, to take down domains that are violating legal requirements or pose a threat to the security and stability of the registry. (See section 3.6.5 of the registry-registrar agreement at http://www.icann.org/en/tlds/agreements/org/appendix-08-08dec06.htm ) The new abusive domain policy clarifies the way PIR will live up to its responsibilities. It is directed at the domains used or misused for phishing, pharming, botnets, distributing malware and other recognized threats to the integrity of the Internet.

In its announcement of the policy, PIR has made it clear that it will continue to work with the registrars on these problems. As in the past, most registrars will respond promptly to known security threats. The new policy spells out the circumstances, probably rare, where immediate action is needed, and for some reason the registrar has not acted. In cases where the domain registrant is the innocent victim of a takeover, PIR will take care that any interruption of service is held to a minimum.

Alexa: I responded to your comment in George Kirikos  –  Jan 09, 2009 9:06 AM PST

Alexa: I responded to your comment in the other topic thread where you made the identical comment (perhaps best to take up the discussion there instead, or feel free to email/phone if you'd ever like to discuss the actual language, and ways to refine the actual text; I'm sure others like registrars or those in the GNSO could work together to improve the wording so that it matches your description of the intentions of the policy, and that innocent registrants receive appropriate safeguards).

Don't forget about IPv6 Derek Morr  –  Jan 20, 2009 12:33 PM PST

Let's not forget about IPv6! IPv6 support was added to the root, and several TLDs added IPv6 glue. At the end of 2008, 206 TLDs (about 75%) had v6-reachable nameservers.

To post comments, please login or create an account.

Related

Topics

New TLDs

Sponsored byAfilias

Cybersecurity

Sponsored byVerisign

DNS Security

Sponsored byAfilias

Domain Names

Sponsored byVerisign

IP Addressing

Sponsored byAvenue4 LLC