We scan new podcasts and send you the top 5 insights daily.
Mockapetris rejected Xerox PARC’s fixed three-level naming because users want freedom to organize information. He designed DNS so names could nest however many levels people needed, noting hidden applications often go many levels deep. If you allow nesting, he argues, support any reasonable amount.
Build products on simple, foundational concepts rather than complex, rigid features. These core building blocks can then be combined and layered, leading to emergent complexity that allows the product to scale and serve diverse needs without being overwhelming by default.
When asked why URLs run from specific to general, Mockapetris calls it an obvious choice. Typing “maps” lets a machine guess “google.com”; typing “com” only narrows the field to hundreds of millions. The order gives autocomplete useful early clues, even if some people think he was wrong.
Mockapetris says DNS’s magic had two parts: it let millions of organizations own separate chunks of the namespace indefinitely, yet users experience one contiguous tree. When looking up a name, the first DNS query asks which name server to consult, not for an IP address.
The classic domain-model hierarchy in OOP is architecturally weak because many essential features, like multi-selecting and editing a common property (e.g., color), are cross-cutting. This forces developers to pollute the base class with accessors, breaking the encapsulation the hierarchy was meant to provide.
Mockapetris copied the SRI host table into DNS every morning, so DNS held all existing names plus new DNS-only entries. Early adopters got both namespaces, while people who stayed on the old host table missed places where the “cool kids” hung out.
Mockapetris explains www began as a convention for pointing to a domain’s web server, alongside names like ftp.stanford.edu for other services. As the web came to dominate, separate service machines faded. The convention stuck even though the original multi-service model mostly died.
Mockapetris recalls writing the first DNS RFCs and getting numbers from his boss, who simply published them on a server for people to download. Today the IETF runs a heavier process with informational and standards-track RFCs, politics, and paperwork—even claiming DNS though it predates the IETF.
In distributed systems, a component's physical location (e.g., a file in a directory) is not proof of its ownership. Responsibility must be explicitly recorded in a central registry. This "record over layout" principle prevents incorrect assumptions, especially for shared resources like scheduled jobs or configuration files.
Mockapetris admits he does not quite understand the economic incentive for running root servers. Early roots were more distributed; now Cloudflare, Google, and other hyperscalers absorb more DNS traffic, partly for speed and prestige, making the system less distributed.
Ivan Sutherland's 1960s Sketchpad used an architecture akin to modern Entity-Component-Systems. Instead of adopting this flexible model, early OOP proponents focused on its hierarchical aspects, leading to decades of rigid domain modeling that struggled with problems Sketchpad had already solved.