Every computer on the ARPANET lived in one hand-edited file — until naming was delegated

the problem

Every host lived in one global table edited by one institute, and the update load was nearing the limit of manageability

background

what everyone would do

Scale the registry itself: hire more staff at the NIC, automate the file edits, distribute HOSTS.TXT faster and more often. Every variant keeps the whole directory in one place and one team's hands, so every added host still adds work to the same centre — growth makes the bottleneck worse exactly as fast as it makes the network bigger.

what they saw

The bottleneck was not the data but its ownership: a directory one institute must edit cannot grow. So editing rights moved to the organisations that already existed, and the centre kept only a map of who to ask.

the move

Mockapetris designed the Domain Name System as a tree of delegated zones: the centre answers only one question — who knows about this part of the tree — and every organisation runs the naming inside its own zone. Names end in a shared top level, authority is cut along administrative boundaries, and answers are cached with time-to-live values, so the system stays fast while no single site holds or updates the whole directory.

why it works

Delegation converts a global consistency problem into many small local ones: each zone's owner updates its own names immediately, without asking anyone, and the rest of the system only needs to know where to ask. Caching with expiries makes repeated lookups nearly free while tolerating the brief inconsistencies that distribution introduces. The centre's workload stops growing with the network at all — it answers 'who knows', a question whose size is fixed, no matter how many hosts exist.

the payoff

DNS replaced HOSTS.TXT, became one of the original internet standards in 1986, and still resolves the entire web today on the 1983 design.

where it breaks

Delegating authority only works when the boundaries you delegate along are real and stable — cut zones where organisations shift and you get ownership fights instead of scale. It also trades away global atomic updates: the system is eventually consistent, and anything that needs the whole world to see one change at one instant has to be built on top of it, not into it. And somebody must still own the root and its trust — the centre shrank, it did not disappear.

what came after

RFC 882/883 is the rare design document whose subject outgrew the network it was written for: the internet scaled by orders of magnitude nobody in 1983 could have planned, and the directory never had to be rebuilt — because nobody at the centre ever had to keep it. Delegation-as-architecture became the template for how the internet grows: solve the coordination problem by handing out authority, not by enlarging the registry.

references

1. [1]RFC 882 — Domain Names: Concepts and FacilitiesRFC Editor, 1983rfc-editor.org
2. [2]Internet Hall of Fame — Paul Mockapetris (documents the HOSTS.TXT bottleneck and DNS adoption)Internet Society, 2012internethalloffame.org

keep it

same kind of clever

• 2011 · Accessible Icon Project (Sara Hendren, Brian Glenney)Changing the official wheelchair symbol would have meant years lobbying a standards body with no reason to act — so the designers skipped the committee and just stuck the new one over the old ones themselves.
• 1979 · NASA / United Airlines (Crew Resource Management)Aviation stopped losing planes to captains who wouldn't listen by making it a subordinate's job to make them
• 1900 · Sanitary District of ChicagoChicago's drinking water was being poisoned by its own sewage at the intake point — so instead of filtering the water after the fact, the city just made its river flow the other way.