Get your free personalized podcast brief

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

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.

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.

Marc Andreessen reveals that early web protocols like HTTP and HTML were intentionally designed as inefficient, text-based formats. This choice, which ran counter to the bandwidth-constrained era, was a bet that making the web "human-readable" via "view source" would foster learning and accelerate adoption.

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.

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.

Surprisingly, legacy websites like Yahoo and Microsoft Bing generate more traffic than ChatGPT. This isn't due to active user preference but the powerful, persistent effect of their position as default search engines and homepages in web browsers.

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.

Andreessen reveals a key design choice for the early web: using inefficient text-based protocols like HTTP and HTML. This bet on human readability and the "View Source" option made the web accessible to developers, creating a virtuous cycle of content creation and demand for bandwidth.

Despite the scramble for new TLDs, the .com domain remains the gold standard. Decades of internet use have trained consumers to associate .com with serious, durable businesses, while newer TLDs like .ai and .si are often linked to spam or less trustworthy sites.

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.