DNS

Sponsored
by

DNS / Most Commented

Come to the First Ever Dedicated New gTLD Conference: .nxt

Sometimes the heavens align. With the release of a number of resolutions from the ICANN Board on Sunday, we learnt two things: One, that there is a determined drive to get the rules for new Internet extensions, gTLDs, finalized in December at a meeting in Cartagena. And two, that the meeting immediately after that - in March 2011 - will be held in San Francisco. more

Moving DNSSEC Forward: Help for Registries, Registrars, ISPs/Hosting, Enterprises, and Name Owners

DNSSEC adoption has been slow, but is now picking up speed, thanks to organizations leading the way. ... While some registries have already signed, some have announced plans to sign and others are still trying to figure out their plan. Either way, DNSSEC is here. How can we make DNSSEC adoption quicker and easier not only for the registry but for individual name owners? more

ICANN May Not Be Perfect, But It Is Working

Though I have been critical of some of ICANN's shortcomings, I remain a strong supporter of ICANN's role as a private sector-led, multi-stakeholder global regulator for the Internet's core addressing systems. My recent blog post about my concerns with the communications processes relating to the addition of the first Arabic script IDN ccTLDs has been quoted in an ITU Staff Paper prepared for the ITU Council Working Group on the World Summit on the Information Society, to be held in Geneva tomorrow. This document seems to suggest... more

IDN and Email: The Harsh Reality

There has been a lot of talk about IDNs here and elsewhere but what does the reality look like for a plain user? As a test, I randomly choose 28 domains from Alexa's top 100 Sites and tried to create a user account with the email address user@??.com. The bleak result... more

Just Say No, to Your ISP Subverting Your DNS Queries

Over the past few weeks I have been seeing reports that some ISP's are actually subverting DNS queries to their own DNS server. Oh the humanity! What this means is that when you (your computer) does a UDP or TCP Port 53 DNS query the ISP is intercepting that and directing it to their own servers. Has anyone been told by their ISP that they are doing this? No? I didn't think so... more

Domain Name Registries Must Do More to Protect Highly-Trafficked Domains

With the recent attacks against high-profile New Zealand domain names including Coca-Cola.co.nz and F-Secure.co.nz, fingers are naturally pointing to Domainz, the registrar of record for these domains, as the party responsible for this lapse in security. While domain name registrars certainly need to ensure the security and stability of their systems, domain name registries must also step up and take responsibility for mitigating risks posed by hackers... more

2008: A Historic Year for DNS

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

Users Don’t Like Forwarded Spam

A message on Dave Farber's Interesting People list complained that Comcast was blocking mail forwarded by DynDNS, a popular provider of DNS and related services for small-scale users... Actually, they're blocking it because a lot of it is spam. This is a problem that every mail forwarder and every mail system encounters; the only unusual thing here is that DynDNS is whining about it. It's yet another way that spammers have broken the mail for the rest of us. more

Censorship: A Threat to the Stability and Security of the DNS?

Censorship practices by governments and other private actors are becoming more increasingly more sophisticated, and their effects are increasingly being felt globally. A case in point, the YouTube incident in Pakistan was a recent example affecting both users and the DNS at a national and global level. Likely other incidents will occur in the near future. As such, I believe censorship should be considered as a threat to the stability and security of the DNS. In the context of Internet governance discussions, I believe the issue should be raised both at ICANN and the Internet Governance forum. Do others agree? more

ICANN: WHOIS Back to Rathole #0

ICANN's GNSO council had WHOIS on its agenda for today. The options on the table: (1) Accepting the outcome of years of policy development processes; (2) rejecting that outcome (again?), but calling for some kind of fact-gathering to feed into future policy work, in order to keep the space occupied; (3) acknowledging that there is broad dissent in the Internet community, and calling for a sunset on the WHOIS clauses in current agreements, as these clauses are not backed by community consensus any more. Not very surprisingly, motions (1) and (3) failed; (2) was accepted; all that after lengthy discussion, with lots of procedural bells and whistles. more

Short Domain Names Threatened by Proposed Policy on IGO Dispute Resolution Procedure

ICANN staff has published a draft report on dispute resolution procedures for IGO (inter-governmental organization) domain names. This proposal has deep flaws and should be rejected by the community, as it does not have the balance and protection of registrant rights present in the existing UDRP. Initially, the proposed policy would apply to new Top-Level Domains (TLDs), but via a Policy Development Process (PDP) it could be extended to existing TLDs. more

If WHOIS Privacy is a Good Idea, Why is it Going Nowhere?

ICANN has been wrangling about WHOIS privacy for years. Last week, yet another WHOIS working group ended without making any progress. What's the problem? Actually, there are two: one is that WHOIS privacy is not necessarily all it's cracked up to be, and the other is that so far, nothing in the debate has given any of the parties any incentive to come to agreement. The current ICANN rules for WHOIS say, approximately, that each time you register a domain in a gTLD (the domains that ICANN manages), you are supposed to provide contact information... WHOIS data is public, and despite unenforceable rules to the contrary, it is routinely scraped... more

Another Whois-Privacy Stalemate

The report of the Whois Working Group was published today. The Working Group could not achieve agreement on how to reconcile privacy and data protection rights with the interests of intellectual property holders and law enforcement agencies. So the Working Group Chair redefined the meaning of "agreement." See the full story at the Internet Governance Project site. more

Temporary Restraining Order Issued Against Domainer’s Use of “mylennar.com”

Companies sometimes find that opportunistic purchasers of domain names (often referred to as "domainers"), will purchase a domain name quite similar to that of the company, and establish a site at the URL loaded with revenue-generating sponsored ads. To accomplish these purposes, domainers seem to prefer the services of companies like HitFarm and Domain Sponsor. A web user types in the confusingly similar URL and is bombarded with pop-up ads and sponsored links to goods and services, often competitive to the company whose name or trademark is being appropriated in the URL... more

The Inextricable Issue of Internationalized Domain Names

ICANN has embarked on the IDN boat at the same time it wants to introduce DNSSEC and new gTLDs. This promises lots of fun. Or grey hair, depending how you look at it. First is the issue of country code IDNs. The ISO-3166 table, based on two letter codes, is a western convention. Some cultures do not use abbreviations or acronyms. Some do not use a character-based alphabet, but a syllabic one. Hence, the next logical step would be to represent the full country name in local script, rather than a transliteration of the ISO string... Imagine the case of India, where there are 1.652 languages, of which 24 are spoken by more than one million people... more