technologybriefs
SubjectsAll subjects on briefs.cloud →
Saved
Systems · Internet culture

Domain Name System

Paul Mockapetris

DNS didn’t make the Internet usable — it made central control impossible.

Worth your time?4.5/5Yes.Study the whole thing.What works, what does not, who it is for ↓
9:22in productionCh. 1 · The hosts file was the bottleneck/ 9:22 · ceiling 15 min
4 chapters · 9:22Ceiling 15:00

The brief is written and checked. The video joins this page when it is cut.4 chapters · 1 min read · 9:22 planned

Read the brief

DNS is the distributed name-resolution system invented by Paul Mockapetris in 1983. It replaced the ARPAnet’s central hosts file. It uses a hierarchical zone model and originally ran over UDP. Later concerns about reliability, security, and privacy drove TCP use and protocol extensions. RFCs 882, 883, 973, 1034, and 1035 define its evolution. Mockapetris implemented the first version, 'Jeeves', for TOPS-20 the same year.

SystemsInternet cultureAbstractionComputingInfrastructureAbstraction across the network →
Chapters & takeaways4
  1. 0:48
    The hosts file was the bottleneck

    DNS replaced the ARPAnet’s brittle, centralised hosts file with a distributed database.

  2. 2:20
    Standardised in four foundational RFCs

    RFCs 882 and 883 defined DNS in 1983; RFCs 1034 and 1035 superseded them in 1987.

  3. 3:58
    UDP first, then TCP — by necessity

    UDP was DNS’s original transport — but reliability, security, and privacy gaps forced TCP and extensions.

  4. 5:22
    Jeeves ran on TOPS-20 before the standards were updated

    Mockapetris built 'Jeeves', the first DNS implementation, for TOPS-20 in 1983.

1 more chapterFewer chapters
Worth your time?

Yes. Study the whole thing.

4.5/ 5
What works
  • delegation across zones
  • separation of naming hierarchy from protocol
  • scalable resolution without central authority
What does not
  • guarantee reliability
  • provide security by default
  • ensure privacy
Study it if
  • network engineers
  • system administrators
  • security practitioners
Skip it if
  • end users who assume DNS is private
  • developers who treat DNS as a secure channel without extensions
Who should study it, and who should skipHide who it is for
The written brief1 min read

What it is and the problem it solves

DNS solves the problem of scaling name-to-address translation beyond a single, centrally maintained hosts file. It enables human-readable domain names to resolve to machine-readable IP addresses across a growing network.

How it works

DNS is a hierarchical and distributed name service that delegates administrative responsibility across zones. It translates domain names to IP addresses using a naming hierarchy and a protocol for data exchange.

What works

The delegation model works: administrative authority is split across zones, avoiding bottlenecks and single points of failure. The separation of naming hierarchy from data exchange protocol allows independent evolution of both.

What does not

DNS does not guarantee reliability, security, or privacy by default. Its original UDP-based design lacked encryption, authentication, and guaranteed delivery — prompting later TCP adoption and protocol extensions.

What it changes

DNS replaced the ARPAnet’s centralised hosts file with a distributed and dynamic database. It shifted name-to-address translation from static, manually updated tables to an automated, zone-delegated system.

Is it worth your time

Yes. DNS remains the foundational infrastructure for Internet name resolution. Its design avoids centralised databases, enabling scalability and resilience that no single-table alternative could support.

Same field · Systems4 of 192
10:24
IPv61996IPv6 delivers on its core architectural promises: vast address space, simplified forwarding, standardised subnets, and host-managed fragmentation. But it does not deliver automatic deployment, backward compatibility, or operational simplicity. Its value is real—but only where the cost of maintaining IPv4 workarounds exceeds the cost of adopting IPv6’s stricter host responsibilities.
10:32
LTE (telecommunication)3GPPLTE is a 3GPP Release 8 standard finalised in December 2008. It replaces GSM/EDGE and UMTS/HSPA radio interfaces and the GPRS Core Network with a new air interface and IP-based Evolved Packet Core. It delivers peak downlink/uplink rates of 300/75 Mbit/s and sub-5 ms radio access network latency. It supports scalable bandwidths (1.4–20 MHz) and both FDD and TDD. It enables seamless handovers to GSM, UMTS, and CDMA2000. Its specifications span hundreds of documents per Release, organised into stages defining service requirements, architecture, and protocol implementation. It became the de facto upgrade path for carriers with both GSM/UMTS and CDMA2000 networks.
9:58
Multiplayer video gameA multiplayer video game is a coordination system—not a genre, not a platform, not an experience. It forces explicit decisions about timing, authority, visibility, and failure mode. Its history is one of repeated adaptation to infrastructure limits, not creative evolution.
10:11
InternetU.S. Department of Defense (DARPA) · 1969The Internet is a system for internetworking—designed to link disparate networks using standardised protocols. DARPA commissioned its core development in the 1970s. TCP/IP standardisation in 1982 enabled global proliferation. Its layered architecture and decentralised governance remain defining features—and enduring constraints.
Up next in Technology

ECC memory

· 9:27

ECC memory doesn’t prevent memory errors—it prevents you from ever knowing they happened unless they’re too big to fix.

Next brief →Back to Systems
9:27