November 1983

DNS standardized

RFCs 882 and 883 defined the Domain Name System in November 1983 — hierarchical names, resolvers, and name servers replacing flat HOSTS.TXT files.

What it was for

DomainNameSystemDNSDomain Name System — translates human-readable domain names into IP addresses. maps human-readable names like `example.com` to IPInternet Protocol — the addressing and routing layer that moves packets across networks. addresses via distributed servers. A resolver asks recursive questions; authoritative servers answer for their zone. Every browser URLUniform Resource Locator — the address that identifies a resource on the web., APIApplication programming interface — a defined way for programs to talk to each other or to a service. call, and email MX lookup still depends on DNSDomain Name System — translates human-readable domain names into IP addresses. — later refined in RFC 1034/1035 and extended with DNSSEC.

Companies

  • IETF

Why it's here

DNSDomain Name System — translates human-readable domain names into IP addresses. solved the scaling crisis of maintaining one giant hosts file for the growing internet.

Why it mattered

Hierarchical domain names became the addressing layer the web and email built on.

What it solved

Flat hostname tables could not scale as ARPANETAdvanced Research Projects Agency Network — the U.S. research network that pioneered packet switching and became a precursor to the internet. merged with other networks.

Media

  • DomainNameSystem
    ImageDomainNameSystem

    Sakari A. Maaranen, CC BY 3.0, via wikimedia

Related