The PublicRoot DNS Operations Working Group (DNSops WG) develops and publishes guidelines concerning the operation and administration of DNS software servers and zone files. These guidelines provide operators and administrators with technical information relating to the implementation of the DNS protocol, zones, resolvers, root and TLD name servers.

The PublicRoot introduces a simple practical architectural solution and countermeasure to reduce unwanted DNS network traffic by deploying the localhost top-level domain.

Peterborough, May 18th, 2005

The PublicRoot DNS Operations Working Group (DNSops WG) is pleased to announce the launching of the localhost Top-Level Domain (TLD) as a solution and countermeasure to reduce unwanted Domain Name System (DNS) network traffic. Over the years localhost traffic has increased significantly as the population of devices connected to the Internet grows.

Incorrectly configured DNS servers and user computer systems generate the unwanted localhost traffic. This results in increased load on root servers and contributes to unwanted network congestion. The localhost TLD is a name label used by every computer on a network to refer to itself. In theory, localhost traffic should never appear on any public or private network.

The PublicRoot will adopt as recommended standards the draft solutions to reduce localhost traffic proposed by the Internet Engineering Task Force (IETF). Peter Dambier, co-chair of the PublicRoot DNSops WG, will co-ordinate the deployment of localhost TLD name servers as a solution. All we need to do, said Dambier, is answer the question, where is localhost, and the answer is always the same, 127.0.0.1.

Over the years, the IETF has debated the implementation of practical countermeasures to localhost traffic congestion. A difference of opinions unfortunately has stood in the way of achieving a viable solution, explained Joe Baptista, Research Director at the PublicRoot. We have two groups at the IETF, he said, one wants to solve the problem via the root servers providing answers, the other sees education of DNS operators as the solution.

Baptista explained the differences contributed to a stalemate in the development of minimum standards that deal with the immediate problem. The PublicRoot supports the continued education of DNS operators but we must address localhost traffic before it gets out of hand, he said. The proactive deployment of localhost infrastructure at the PublicRoot should see immediate savings in bandwidth to network providers and reduced load on the root servers.