Skip to content

Domain Name System Introduced

November 1983.Networking.Standard published.Date precision, month.Evidence grade, primary.4 primary sources

Drivers:

Scalability demandInteroperability need

The HOSTS.TXT approach could not scale beyond a few hundred hosts. The internet's growth demanded a distributed naming system that could handle millions of names with decentralised administration.

DNS is like the internet's phone book. When you type 'google.com' into your browser, DNS looks up the actual numeric address (IP address) of Google's servers. Without DNS, you would have to remember numbers like 142.250.187.46 instead of website names.

Domain Name System Introduced event plate

Structured atlas record showing date, domain, evidence grade, source count, and predecessor and successor links.

Event plate: Domain Name System Introduced Convergence-divergence layout. The central hero card carries the event year, type, title, evidence grade, domain and era band. 0 predecessor cards on the left feed in with red arrows labelled "absorbs". 0 successor cards on the right derive with red arrows labelled "spawns". Key terms below the hero pin the vocabulary the event introduced. EVENT PLATE Source: https://www.rfc-editor.org/rfc/rfc882 1983 - STANDARD PUBLISHED Domain Name SystemIntroduced primary evidence Domain: AI and machine learning Era band: E6 AI-scale systems KEY TERMS - VOCABULARY THE EVENT INTRODUCED DNS domain name nameserver resolver Convergence-divergence: predecessors absorbed, successors spawned Hero card carries year, evidence and domain. 0 predecessors flow in from the left; 0 successors flow out to the right. Key termsbelow pin the vocabulary the event introduced.

Forecasts and counterfactuals stay labelled as opinion in the event data. Source: Computer History Museum.

Before

The early internet used a single HOSTS.TXT file maintained by SRI-NIC to map hostnames to IP addresses. As the network grew, this centralised approach became unsustainable. Updates were slow, the file grew unwieldy, and there was no hierarchy for organising names.

What changed

The Domain Name System (DNS) replaced the flat HOSTS.TXT file with a distributed, hierarchical naming system. DNS introduced domain names (like example.com), delegated authority through a tree structure, and allowed names to be resolved through a network of nameservers.

How it happened

Paul Mockapetris at USC's Information Sciences Institute designed DNS and published the specification in RFC 882 and RFC 883 in November 1983. The design introduced the concept of zones, authoritative nameservers, and recursive resolution. RFCs 1034 and 1035 (1987) refined the specification and remain the foundational DNS documents.

Outcomes

  • Enabled scalable naming for millions of internet hosts
  • Created the familiar .com, .org, .net domain structure
  • Established distributed database model adopted by other systems
  • Made the internet usable for non-technical users

Limitations

  • Original DNS had no authentication, enabling spoofing attacks
  • DNS resolution adds latency to connections
  • Centralised root server management created governance debates
  • DNS caching can delay propagation of changes

Lessons learnt

  • Hierarchical delegation enables massive scalability
  • Caching is essential for distributed system performance
  • Security must be designed in from the start (led to DNSSEC)
  • Naming systems become critical infrastructure

Stakeholders and artefacts

Organisations

  • USC Information Sciences InstituteacademiaDesign and specification
  • SRI-NICacademiaOperated original naming service
  • IANAstandards_bodyRoot zone management

Individuals

  • Paul MockapetrisDesigner, USC ISIDesigned DNS, authored RFCs 882, 883, 1034, 1035
  • Jon PostelAdvisor, USC ISISupervised DNS development, managed IANA

Artefacts

  • DNSprotocolDistributed hierarchical naming system for internet resources
  • Domain NamespecificationHuman-readable identifier like example.com
  • NameserversoftwareServer that resolves domain names to IP addresses

Key terms

DNSdomain namenameserverresolverzoneTLD

Causality

Preceded by: TCP/IP Protocol Suite Specified.

Made possible: World Wide Web Invented.

On this course

Read in the path How the Internet Works.

Sources

1Paul Mockapetris. "RFC 882: Domain Names - Concepts and Facilities". ISI, 1983-11.authoritativewww.rfc-editor.org/rfc/rfc882
2Paul Mockapetris. "RFC 883: Domain Names - Implementation and Specification". ISI, 1983-11.authoritativewww.rfc-editor.org/rfc/rfc883
3Paul Mockapetris. "RFC 1034: Domain Names - Concepts and Facilities". ISI, 1987-11.authoritativewww.rfc-editor.org/rfc/rfc1034
4Paul Mockapetris. "RFC 1035: Domain Names - Implementation and Specification". ISI, 1987-11.authoritativewww.rfc-editor.org/rfc/rfc1035