DNS |
Sponsored by |
|
Internet Systems Consortium (ISC), formerly Internet Software Consortium, has changed its name to better reflect the new direction of the organization. The renamed company has expanded the mission of the original ISC to include more focus on Global DNS operations. In addition to developing and maintaining production quality Open Source software, such as BIND and DHCP, ISC will now enhance the stability of the global DNS through reliable F-root nameserver operations and ongoing operation of a DNS crisis coordination center, ISC's OARC for DNS; and further protocol development efforts, particularly in the areas of DNS evolution and facilitating the transition to IPv6. more
For the first time in Internet history the number of instances of DNS root servers outside the United States has overtaken the number within. The balance was tipped by the recent launch in Frankfurt of an anycast instance of the RIPE NCC operated K-root server. The K-root server is one of the 13 DNS root servers that resolve lookups for domain names all over the world and form a critical part of the global Internet infrastructure. The K-root server has been operated by the RIPE NCC since 1997 when the first server was installed at the London Internet Exchange (LINX) in London, UK. more
I just wanted to call people's attention to this International Chamber of Commerce (ICC) paper on Internet governance. I don't endorse it; haven't actually read it yet, but their say will play a big role and should be widely known: "Coming barely a month after the World Summit on the Information Society (WSIS) in Geneva, and prepared by ICC's Commmission on E-Business, IT and Telecoms, the paper divides the issue of Internet governance into three main components - technical engineering, coordination of the names and numbers system and public policy matters." more
CRE notified Dr. Twomey, President and Chief Executive Officer of ICANN, of the applicability of the Data Quality Act to ICANN in a detailed letter of October 29th. CRE asked ICANN for a meeting to discuss the issue of the applicability of the Data Quality Act to ICANN since CRE received no communication in response to the letter. In mid-December ICANN agreed to a January 23rd meeting with CRE. Notwithstanding CRE's trip to ICANN's headquarters in California for the scheduled meeting, the organization refused at the last moment to meet with CRE. CRE now knows how Dr. Twomey felt when he was expelled from an ICANN-related planning meeting in Geneva. more
ICANN's Security and Stability Advisory Committee (SECSAC) recently released some recommendations regarding the DNS infrastructure, specifying among other things, that sub-zone delegation be kept up-to-date. ...The SECSAC report doesn't mention, but I believe is trying to address, is the alarming fact that nearly 10% of the name servers listed in the root zone are lame, either they aren't authoritative for the zones they are supposed to be, or they are unreachable much of the time.
more
ICANN has launched three task forces on WHOIS restructuring...It sounds innocuous enough -- nobody likes spam -- but the restrictions being discussed reach further than marketers. Pushed by registrars who feel that WHOIS amounts to forced disclosure of their customer lists, the task force is seriously discussing closing off port 43's straightforward access to WHOIS information, replacing it with GIF-based barriers or similar access restrictions. more
Please do sit down. Should the shock cause you to suddenly lose consciousness, I hereby disclaim all responsibility for any subsequent loss or injury. I'm about to defend the anthrax of the Internet: NAT. Network Address Translation is a hack to enable private IP addresses on one side of a router (inside your network) to talk to public IP addresses on the other side (on the Internet, outside your network). It really doesn't matter how it works. The consequence is that unless the router is specifically configured, outsiders can't get in uninvited. So those on the inside can't, by default, act as servers of any service to the outside world. more
In December 2003, the testing phase of Multilingual domains also known as Internationalized Domain Names (IDN), went live with the addition of over 350,000 multilingual domains to the .com and .net registries. As of 1st January 2004, the .com registry contained 300,409 IDN's, whereas the .net registry had 79,630 IDN's, representing around 1.25% of the total .com and .net domains. WebHosting.Info has analyzed these 380,039 IDN domains that are now live, and provided a detailed insight on trends and patterns across these domains. more
The National Academy of Sciences (NAS) has been studying the issue of Internet navigation and the DNS. The study was undertaken at the request of Congress to "provide analysis and advice for consideration by agencies of the U.S. Government, interested international institutions, and other stakeholders." In addition to examining technological issues, the study is also considering "relevant legal, economic, political, and social issues...because technologies related to the DNS and Internet navigation do not operate in isolation, but must be deployed within a complex and challenging national and international context." more
The Council of European National Top-Level Domain Registries (CENTR) announced today their response to Professor Michael Geist's draft survey report "Government and country-code top level Domains: A global survey", which was conducted on behalf of the International Telecommunication Union (ITU) in December 2003. "In the last decade the general trend has been to de-regulate markets in the Communications Industry, which continues to stimulate economic growth and innovation, and it seems perverse that this ITU supported report is seeking to go against the proven successful trend," said Paul Kane, chairman of CENTR. more
RFID tags, UPC codes, International characters in email addresses and host names, and a variety of other identifiers could all go into DNS, and folks have occasionally proposed doing just that. Its really just a question of figuring out how to use the DNS -- its ready to carry arbitrary identifiers. And by the way, this isn't a new idea, see RFC 1101 for proof, although even earlier I designed the DNS in the early 1980s to allow it to be so, but it seemed too far fetched to document for a while. ...I was in Geneva for a WSIS meeting of CTOs, and was surprised that the various organizations (ITU, ICANN, ISOC) haven't figured out that they need each other to make this technology work, rather than asserting ownership. more
While this may be better suited as a comment to the CENTR posting, I thought that its length might warrant a separate submission. Many thanks to CircleID for hosting this interesting discussion. Below is the full text of a comment I forwarded to CENTR earlier today in reply to its commentary on my recent study on national governments and ccTLDs. ...I should also preface my remarks by noting that I speak for myself -- not the ITU (see below), nor CIRA, (a CENTR member ) on which I serve on the board of directors, nor the Public Interest Registry, which manages the dot-org domain and on which I serve on the Global Advisory Council. more
Harvard Law School's distinguished Berkman Center for Internet & Society has published a preliminary study, "Public Participation In ICANN." ...The problem with the preliminary study is that it fundamentally misunderstands the role of ICANN in Internet governance. Specifically, ICANN's duty is not and should not be to simply carry out the will of the "Internet user community." Instead, ICANN's duty is to carry out the responsibilities the organization agreed to in its Memorandum of Understanding (MOU) and contract with the Department of Commerce. This does not mean that ICANN should exclude stakeholder views. more
Stratton Sclavos of VeriSign distills the essence of the SiteFinder controversy in his CNet interview...There is a subtle but essential misunderstanding here. Innovation can and should happen in Internet infrastructure, but there are a handful of core elements that must remain open and radically simple if the Internet is to remain, well, the Internet. These include TCP/IP, SMTP, HTTP, BIND, BGP, and the DNS (especially the .com registry). Any change in these protocols should be very carefully vetted through a consensus-based process. more
According to RFC1034, "cnn.com" and "cnn.com." should be the same domain names. However, it doesn't appear that programmers always understand that trailing dots can be added to domain names. Web servers also can't seem to agree what to do with a period at the end of a host name. IIS, thttp, and Akamai's Web server all get confused while Apache doesn't seem to care. How much other software behaves incorrectly because of a trailing period on a domain name? Can spam-filtering software be bypassed with dotted email addresses? Here is a situation when bad things can happen -- "WebShield SMTP infinite loop DoS Attack"... more