DNS |
Sponsored by |
Every IT person has some interaction with a DNS server, even if it is not managing it. Most DNS servers, certainly the majority are sitting in some closet or rack somewhere dutifully running and collecting dust. Like a certain battery operated bunny, these services just keep on running. The durability of DNS (Domain Name System, that is) is a testimony of just how well it was designed... How often do you think about your DNS server? Here is my plan for how to keep your relationship with your DNS server alive and well.
The ICANN Implementation Recommendation Team (IRT) working group has published its final report, which I decided to analyze a bit further. I already made a few comments last month, both in the At-Large Advisory Council framework and on my own. There are several issues raised by the recommendations of this report. The Uniform Rapid Suspension system (URS) is one.
Before we get into what DNSSEC is and the benefits of it, let's talk about some of the other potential pitfalls of DNS. One of the most significant issues we have to deal with are denial-of-service (DoS) attacks. While DoS attacks are not specific to DNS we have seen DNS be a frequent target of these attacks.
I gave a talk yesterday at Northwestern called A DNS in the Air. My idea is that, in order to scale, the emerging wireless Internet needs something analogous to the domain name system (DNS) -- the infrastructure that allows you to reach sites across the Net. Billions of mobile phones, and even more billions of connected sensors and other wireless devices will completely overwhelm our current spectrum management regime. AT&T Wireless estimates we will need between 250 and 600 TIMES the current wireless capacity in 2018, less than a decade from now.
ICANN staff recently posted on its website an updated timeline on the new gTLD process. Attempting to be "fair and balanced," I see some good, some bad, and some potential ugly in this timeline. I know there are a lot of good people at ICANN working very hard to conclude the Herculean task of implementing the new gTLD process. However, ICANN just can't help shooting itself in the foot with poorly worded and ambiguous statements...
Viviane Redding, the Information Society and Media Commissioner for the EC posted a video blog this week noting that the JPA between ICANN and the US Department of Commerce ends this September. In it she proposes that ICANN be overseen by a "G-12 for Internet Governance" with 12 geographically balanced government representatives from around the world. That's such a non-starter that I'm baffled that she would even propose it...
News broke this week about an attack in Puerto Rico that caused the local websites of Google, Microsoft, Yahoo, Coca-Cola, PayPal, Nike, Dell and Nokia to be redirected for a few hours to a phony website. The website was all black except for a taunting message from the computer hacker responsible for the attack...
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...
The NTIA has published a Notice of Inquiry, Assessment of the Transition of the Technical Coordination and Management of the Internet's Domain Name and Addressing System, in advance of the expiration of the Joint Project Agreement in September 2009. The document outlines the history and evolution of the Memorandum of Understanding (MOU) between the Department of Commerce (DoC) and ICANN, and the questions posed cover fairly standard territory. However, the following might be worth paying attention to...
This past February, around 100 DNS industry experts met in Atlanta, GA for the "The Global DNS Security, Stability, & Resiliency Symposium." Organized by ICANN and hosted by Georgia Tech, this event was to strengthen personal relationships between operators and review what we know about the DNS infrastructure... The content included three breakout groups over two days: Enterprise Use of DNS, DNS in Resource Constrained Environments, and Combating Malicious Use of DNS...