DNS

Sponsored
by

DNS / Most Commented

IDN Evolution Discussed at ICANN Cartagena

Internationalized domain names (IDNs) have been available to Internet users for many years, but this year the first fully non-Latin IDN domains have become enabled by ICANN and country-code top-level domain registries. The recent success of the launch of Russia's .?? (.rf) ccTLD shows that there is an enormous demand for domain names in Internet users' native languages. more

The Next Internet Revolution Will Not Be in English

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. more

.COM - The Riskiest Top-Level Domain? (Part 2)

Following up from my post yesterday, I thought I would take a look at how spammy each particular TLD is. At the moment, I only track 8 TLD's - .cn, .ru, .com, .net, .org, .info, .biz and .name. To check to see which one is the spammiest, I took all of our post-IP blocked mail and determined how many times those messages occurred in email, and how many times that email was marked as spam... more

Reduce the Risk of URL Shorteners to Your Brand With Your Own TLD

A very real and potentially dangerous issue for brands is the continual reliance on obscure country code domains for URL shortening services. Recent reports have emerged that the country code domain .ly will no longer allow domains with 4 or less characters to be registered by users outside of Libya. What exactly does that mean for marketers that are using popular URL shorteners like bit.ly and ow.ly today? It means more risk. As a brand owner who is spending thousands or even millions of dollars on your social media campaigns, the solution is very simple - get your own top-level domain, and control your own destiny. more

Libyan Government Seizes vb.ly Domain

The one-page link shortening service provider, vb.ly, has been seized with no apparent warning by the Libyan government which manages the ".ly" county code Top-Level Domain (ccTLD). According to reports, Nic.ly, the registry operator of the ccTLD in Libya informed the user of the domain that the content of its website was considered offensive, obscene and illegal by the Libyan Islamic Sharia Law and therefore revoked. more

DNSSEC vs DDoS Protection: Is It Really a Choice?

Within the last year or two, I've heard people express an opinion to the effect that if the domain name industry put as much focus on preventing distributed denial of service attacks as we have on implementing DNSSEC, the Internet would be a safer place. While there may be a grain of truth there, I suggest that this kind of thinking presents us with something of a false dichotomy. more

The Window of Opportunity for ccTLDs

The announcement that .co has already achieved over 450,000 new registrations since the opening up of the second level a month ago demonstrates that there is strong demand in the global domain name marketplace for quality new domain spaces. Though .co is the country code Top Level Domain (ccTLD) for Colombia, the second-level registrations (i.e. company.co) are available on a global basis and it is being pitched as a direct competitor to the dominant .com gTLD. Google has altered its algorithm to increase the relevance of search results in the .co domain by treating .co as a gTLD... more

IPv6 “Ripeness”: The Hard Numbers on ISPs and Deployment Rates

As the unallocated IPv4 address pool runs out, are Internet Service Providers (ISPs) actually deploying IPv6? The graph, first in a series from RIPE Labs, looks at the IPv6 "ripeness" of all ISPs registered as RIPE NCC members. We created a rating system that gives ISPs up to four "stars" for IPv6 services that they provide, based on the following criteria... more

VeriSign Anti-Trust Lawsuit Paves Way for More Suits If There Are No Vertical Integration Exceptions

The Coalition for Internet Transparency (CFIT) filed an anti-trust suit against VeriSign for their monopoly control of the .COM registry and the expiring market of .COM domains. The claims were many including excessive financial pressure lobbying and lawsuits to force ICANN into renewing the VeriSign .COM agreement under very self-serving terms. ICANN inevitably was paid millions of dollars to settle the suit. However, the saga continues once again. ... In the light of continuous and relentless discussions and proposals by the Vertical Integration working group, one question is in the back of everyone's mind. Could the decision on Vertical Integration backfire on ICANN and invite similar suits in the domain name space? more

One Billion Internet Users

Last week ICANN took another very significant step forward in the expansion of the internet by approving the delegation of a number of Chinese script IDN ccTLDs. Although we have all heard statements that portray the introduction of IDN ccTLDs as being perhaps the single most important factor in the achievement of ICANN's "One World, One Internet" vision, we should take a moment to appreciate the true significance of this latest round of IDN ccTLD approvals. more

DNS Platforms: A Study in Capacity and Scalability

Capacity and scalability are necessary in managing DNSSEC and D/DoS. Capacity, necessary for maintaining operations during D/DoS attacks, is also necessary for increased traffic due to DNSSEC deployment. Scalability is highly important, as DNSSEC is deployed not only will greater traffic levels will be encountered, greater demand will be placed on the DNS platform. In the interest of understanding both capacity and scalability CommunityDNS conducted tests to assess the readiness of the two main DNS server platforms, BIND and NSD... more

Towards a DNSCERT Definition

To mix metaphors, my e-mail has been ringing off the hook after my previous article and I've had to think deep and difficult thoughts about what we really mean by DNSCERT, and whether DNS-OARC really has the capability or really can grow the capability to operate such a thing. I've had some discussions with ICANN and with members of the DNS-OARC board and staff, and it's time I checkpointed the current state of my thinking about all this. more

What is ‘On-Tap’ at ICANN 38 - Brussels (There’s More to Belgium than Beer!)

As the shorter of the ICANN interregnums comes to a close and the ICANN faithful finalize their dinner reservation agendas for Brussels, it is time again for a preview of what will be 'on-tap' at next week's ICANN meeting. While, as always, there is a lot going on in ICANN Land, a scan of the blogosphere and ICANN list serves suggests that the four most discussed topics will be... more

Who is Blocking WHOIS?

On April 16 ICANN issued a breach notice to Turkish Registrar Alantron for not consistently providing access to its WHOIS database via Port 43, a command-line query location that all Registrars are required to supply under conditions of their contract with ICANN under section 3.3.1. Four days later they issued a breach to Internet Group do Brazil for the same problem. ... The WHOIS record, as we all know, is a massive fraud with illicit parties filling records with bogus information and hiding behind anonymity. more

Deploying DNSSEC: Lessons from Domain Registrar Implementation

As a registrar at the front end of the DNSSEC deployment effort, our technical team has made a sustained investment in DNSSEC deployment so that our customers don't get overwhelmed by this wave of changes to the core infrastructure of the Domain Name System. Along the way, we've learnt a lot about how to implement DNSSEC which might hold useful lessons for other organizations that plan to deploy DNSSEC in their networks. more