DNS
The history of the Domain Name System begins with a file. A simple text file called HOSTS.TXT that the SRI Network Information Center laboriously distributed across ARPANET in the early 1980s. This makeshift solution worked as long as the network remained limited to a few dozen machines, but the explosion in the number of connected computers transformed this system into an administrative nightmare.
Paul Mockapetris and his team at the USC Information Sciences Institute observed this drift with concern in 1982. The HOSTS.TXT file grew larger every day, its distribution was costly, and nobody could keep up with the pace of modifications. Technological evolution worsened the situation: whereas the original ARPANET primarily connected shared central systems, the arrival of individual workstations exponentially multiplied the number of machines to reference. The scale shifted from the number of organizations to the number of users—a dizzying prospect for the time.
Faced with this impasse, Mockapetris explored existing alternatives. He studied IEN116 from DARPA Internet, examined XEROX's Grapevine, but no system truly met the specific needs of the Internet. The team then decided to design an entirely new architecture, distributed by nature: the Domain Name System. The first specifications appeared in 1983 in RFCs 882 and 883, technical documents that would transform the Internet.
The central idea of DNS lies in its tree structure. Each node of the tree carries a label, and a computer's full name is constructed by ascending from node to node up to the root. This natural hierarchy makes delegation of authority elegant because each organization manages its portion of the namespace without depending on a central body for routine modifications. The first top-level domains reflected this pragmatic philosophy: .edu for education, .com for businesses, .fr and .uk for countries.
The technical architecture rests on two pillars. On one side, name servers store and distribute information for their zone of responsibility. On the other, resolvers integrated into client systems query these servers to locate the requested information. Between the two, a sophisticated caching system temporarily stores responses according to a time-to-live defined by each administrator. This caching constitutes DNS's performance secret: it avoids endlessly repeating the same queries to distant servers.
The transition from HOSTS.TXT did not happen overnight. The University of Berkeley took the lead in 1985, becoming the first organization to completely abandon the old system in favor of DNS. This pioneering migration immediately revealed practical problems: users struggled to adapt to new addressing formats, applications had to be reprogrammed to handle temporary failures inherent in any distributed system.
In 1987, approximately 300 domains had been delegated by the SRI-NIC. A year later, this number already exceeded 650, including 400 for normal namespaces and 250 for network address spaces. Seven root servers ensured the system's global redundancy, judiciously distributed across the Internet's main backbone networks. This exponential growth validated Mockapetris's intuitions: DNS absorbed without difficulty a load that the old system could never have supported.
The 1990s saw DNS usage explode with the arrival of the Web and the democratization of the Internet. The system proved its robustness in the face of this unexpected surge in demand. New record types were progressively added to handle new functionalities, such as MX records that revolutionized email routing. One of the protocol's major strengths lies in this capacity for evolution without breaking compatibility.
But success also attracted malicious interest. In the early 2000s, cache poisoning attacks (DNS spoofing) multiplied, and domain hijackings made headlines in specialized publications. The technical community responded with cryptography through DNSSEC, a protocol for securing DNS exchanges. Its deployment began symbolically in 2010 for the DNS root, before progressively extending to top-level domains and then to organizations.
Internationalization raised other issues, both technical and political. How could Chinese, Arabic, or Russian users be allowed to use their own characters in domain names? IDNs (Internationalized Domain Names) provided an elegant answer in the 2000s, but their implementation required profound modifications to ensure compatibility with billions of existing systems.
DNS governance underwent a major evolution in 1998 with the creation of ICANN. This non-profit organization took over from the U.S. government to coordinate the global domain name system. ICANN oversees the allocation of new top-level domains, establishes naming policies, and attempts as best it can to reconcile technical and commercial interests.
Between 2012 and 2024, DNS went through a new expansion phase. ICANN's new gTLD program released hundreds of novel extensions: .shop, .paris, .blog, and thousands of others. Simultaneously, privacy concerns drove the development of DNS-over-HTTPS and DNS-over-TLS. These protocols encrypt DNS queries, limiting the possibilities for surveillance and censorship by intermediaries.
Forty years after its conception, DNS continues to operate on its original principles. This exceptional longevity is explained by Mockapetris's architectural choices: favoring simplicity over sophistication, flexibility over premature optimization. The caching mechanisms and hierarchical distribution of authority remain relevant despite technological evolution. DNS illustrates how an infrastructure can grow while preserving its compatibility with existing systems.
In 2024, DNS manages billions of domain names and responds to hundreds of billions of daily queries. This invisible infrastructure supports all global Internet traffic. Its current challenges concern security against denial-of-service attacks, query privacy, and root server resilience.
The DNS adventure tells how a technical innovation can restructure the Internet's architecture, transforming a simple directory into a critical global infrastructure. Its modular and evolutionary design is a model for all protocols aspiring to longevity on the Internet.