Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

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.

Related Insights

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.

This autonomous governance protocol manages everything from adding node providers to upgrading the core protocol. It operates via proposals and a liquid democracy system, removing the need for a centralized administrative body.

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 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.

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 calls DNS a possible privacy risk but says web advertising violates privacy far more effectively. He notes that when an ad loads, 150 or more organizations may be asked whether to serve it, using up to 144 characteristics about the person.

The blockchain ecosystem is not a single network but many fragmented 'zones' with different rules, much like the early internet. Cross-chain interoperability protocols serve the same function as TCP/IP, providing a standardized messaging layer to connect these disparate public and private chains, creating a cohesive network from fragmented parts.

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.