DNS

India: One Country, Many Internationalized Domain Names

If you're interested in learning more about Internationalized Domain Names (IDNs), UNESCO and EURid recently released a report on the evolution and challenges of IDNs. It's a good read and it highlights some of the struggles that countries and registries face and taking IDNs mainstream. Though Russia has so far proven to be a major success story - with more than 800,000 IDN registrations so far (and counting) - most other IDNs are have a long ways to go yet.

New gTLDs: Will Application Developers Be Ready In Time to Secure User Confidence?

Last week I pointed out a potential problem with the user experience, if, as envisioned, a large number of new generic Top-Level Domains (gTLDs) are added to the root at the same time. The problem I was referring to has nothing to do with the new gTLDs themselves. Rather, it's about the lack of any updated procedures and communication campaigns to application and software vendors. The objective would be to alert them in time and equip them to swiftly update their programs...

ICANN Releases gTLD Applicant Guidebook

Per their timeline, ICANN released the gTLD Applicant Guidebook on May 30th. This version contains revisions based upon both community feedback, as well as recent consultations with the Governmental Advisory Committee (GAC).

Anycast, Unicast, or Both?

A long time ago in an Internet far away, nobody paid for DNS services. Not directly at least. We either ran our own servers, or got DNS service as part of our IP transit contract, or traded services with others. In ~1990 I was the operator of one of the largest name servers in existence (UUCP-GW-1.PA.DEC.COM) and I exchanged free DNS secondary service with UUNET. Two thousand zones seemed like a lot of zones back then -- little did we dream that there would some day be a billion or so DNS zones world wide.

The gTLD Boondoggle

I've been watching at the excitement build in the domain community, where a lot of people seem to believe that at next month's Singapore meeting, by golly, this time ICANN will really truly open the floodgates and start adding lots of new Top-Level Domains (TLDs). I have my doubts, because there's still significant issues with the Governmental Advisory Committee (GAC) and the US Government and ICANN hasn't yet grasped the fact that governments do not defer to NGOs, but let's back up a little and ask is this a good idea.

Who Broke the WHOIS?

As Internet services go, WHOIS held a lot of promise but has repeatedly failed to live up to its potential; raising the question "is it time to retire WHOIS?" The concept behind WHOIS was simple. For each and every registered domain name, provide the facility for querying details about who owns it, who administers it, when was it created and when it will expire. Unfortunately the service lost its way practically from day one after failing to agree upon or adhere to any formal structure of the content it provides.

The User Experience with New TLDs: How to Avoid the Junk Mail File or ‘User Unknown’

As new Top-Level Domains (TLDs) are launched, the industry mustn't overlook the customer experience. A key question is this: Will the software applications we all use, recognize the new TLDs and know what to do with them in a timely fashion? Think email and even form-fill applications. I speak from experience here. In 2006 when we launched the .MOBI TLD, there were arguably only a handful of .MOBI email addresses in existence. To my dismay, I found that often emails sent only from my .MOBI account were not being received at the other end...

IPv6 RIPEness: One Year Later

A year ago, the RIPE NCC introduced IPv6 RIPEness -- a system that rates IPv6 deployment of Local Internet Registries (LIRs)... Now, one year later, the numbers have gone up... In absolute numbers: more than 3,000 LIRs have IPv6 address space. This means that the RIPE NCC has made more than 1,100 IPv6 allocations within 12 months.

Responsibilities of the DNS: “Oh YES you will!”, “Oh NO you will not!”

What is the responsibility of the DNS? Should the DNS be responsible for policing traffic across its infrastructure? Should the blocking and blacklisting of names or throttling of query packets be the responsibility of the DNS? From experience I know my opening paragraph has started passionate debates in more than one section of this globe. We at CommunityDNS have found ourselves right in the middle of such heated debates. "Oh YES you will!", "Oh NO you will not!"

Open letter to US House Subcommittee for Oversight Hearing on gTLDs

This is an open letter to the United States House Subcommittee on Intellectual Property and the Internet regarding the Oversight Hearing on new Top-Level Domains to be held on Wednesday 4 May. The intention of the open letter is to highlight the imbalance of intellectual property interests on the panel and to ensure the Subcommittee is presented with some balanced facts and benefits of the new Top-Level Domain program.