The Man Behind the Hidden Levers of the Internet
Jon Postel wasn’t a billionaire. He didn’t work for Google or Apple. He spent his career at the University of Southern California’s Information Sciences Institute, a quiet research hub where real infrastructure was built, not hype. His title? Officially, not much. Unofficially? He was the Internet’s first librarian, gatekeeper, and occasionally, referee. He managed the Internet Assigned Numbers Authority (IANA) from a desk in Marina del Rey, California, starting in the 1970s. That meant he oversaw the core directories of the Internet: IP addresses, port numbers, and most importantly, the domain name system (DNS) root zone. Think of it like this: if the Internet were a city, Postel wasn’t the mayor. He was the guy who decided which streets got which names—and who made sure no two streets had the same one. And that’s not a small job. We’re talking about coordination across thousands of networks, universities, governments, and later, corporations.
Here’s the thing: in those early days, there were no formal rules. No treaties. No global regulatory bodies. Decisions were made through a kind of gentleman’s agreement, an unspoken code of trust. And Postel? He was the one everyone trusted. He wasn’t flashy. He didn’t seek power. But he had it—because people gave it to him. That changes everything when you realize how much of the Internet’s early stability rested on personal integrity, not law.
How One Man Prevented a Digital Coup in 1998
In 1998, a company called Network Solutions held a U.S. government contract to manage domain name registrations. Then, without warning, the U.S. Department of Commerce tried to hand control of IANA to them permanently. No public process. No international consultation. Just a quiet transfer of power to a for-profit entity. That’s when Postel did something extraordinary. He sent an email—just one—to eight of the twelve root server operators around the world. In it, he asked them to redirect their systems to a new root server, one under his control at USC. Within days, it was done. A shadow DNS system went live. The Internet didn’t crash. But the message was clear: the infrastructure wasn’t owned by any government or corporation. It answered to coordination, not authority.
And then? The U.S. government backed down. Seriously. They reversed course. Within weeks, Postel was pressured to revert the change. Which he did. But the point had been made. The system could be decentralized. It could resist capture. Because one man, with no army, no budget, just credibility and a mailing list, had shown that power could be reclaimed. That was October 1998. He died a month later, at age 55, from surgical complications. Some call it a coincidence. I find this overrated. The timing? Suspicious. The stress? Immense. He had just stared down the U.S. government to defend a principle—and won. But at what cost?
The Email That Shook the Digital World
Postel’s famous message was short. Calm. Technical. No drama. But its implications were nuclear. He framed it as a test. “We are doing root server tests,” he wrote. But everyone knew better. The root servers are the foundation of DNS—they tell your browser where “google.com” actually points. Changing their configuration isn’t a test. It’s a switch of the master key. Eight out of twelve operators complied. Not because they had to. Because they believed in him. That level of trust doesn’t exist today. You can’t replicate it. It was cultivated over 25 years of quiet stewardship.
Why This Wasn’t Just a Technical Move
To call this a “networking incident” is like calling the fall of the Berlin Wall a “border control adjustment.” It was political. Symbolic. A statement that the Internet belonged to no single nation. The U.S. had assumed de facto control since its origins in ARPANET. Postel’s action said: not anymore. And he did it without firing a shot, without mobilizing armies—just an email and a shared sense of duty among engineers who, back then, still saw the net as a commons, not a commodity.
Postel’s Law: Do What You Must, Allow What You Can
Long before the 1998 incident, Postel had already shaped the Internet’s philosophy. His famous maxim—“Be conservative in what you send, be liberal in what you accept”—became known as Postel’s Law. It guided how software should communicate: don’t break connections over minor errors. Be forgiving. Allow growth. This wasn’t just code. It was ethics. It encouraged interoperability. It allowed innovation to flourish without rigid control. But here’s the irony: the same principle that made the Internet resilient also made it vulnerable to abuse. Spam, malware, spoofing—many exploits work because systems are too “liberal” in what they accept. So was Postel naive? Or was he right for his time? The issue remains unresolved.
That said, the law reflects a worldview we’ve largely abandoned. Today’s systems prioritize security over openness. Zero-trust architectures. Firewalls. Encryption by default. All good things. But we’ve lost something too—a culture of cooperation, of mutual respect among strangers building something bigger than themselves. And that’s exactly where the nostalgia kicks in. Not for the technology. For the ethos.
Could One Person Do This Today?
Let’s be clear about this: no. The Internet has grown too vast, too commercialized, too politicized. In 1998, there were about 147 million users. Today? Nearly 5 billion. Back then, control was informal, almost accidental. Now, it’s a global battleground involving ICANN, the ITU, the U.N., tech giants, and nation-states. One person can’t just reroute the root servers with an email. The system is designed to resist exactly that kind of unilateral action. Which is good. But also, kind of sad. We’ve traded agility for stability. Safety for bureaucracy.
Compare it to modern attempts at centralization. When Facebook rebranded as Meta and pushed the metaverse, critics warned of corporate enclosure. When China developed its own sovereign Internet, complete with a parallel DNS, it showed how fragmentation is possible. But no single figure today commands the moral authority Postel had. Not Tim Berners-Lee. Not Vint Cerf. Not even Edward Snowden, despite his revelations. The age of the trusted technocrat is over. Or maybe we just haven’t found the next one yet.
ICANN vs. Community Trust
The Internet Corporation for Assigned Names and Numbers (ICANN) was created in 1998, partly in response to the Postel incident. It was supposed to internationalize control. In theory, it’s a multi-stakeholder model. In practice? It’s slow, opaque, and often influenced by powerful interests. Postel’s informal authority was replaced by committees, by process, by lobbying. Is it better? More democratic? Maybe. But is it faster? More trustworthy? Data is still lacking. Experts disagree. Honestly, it is unclear.
The Myth of Decentralization
We love to say the Internet is decentralized. But is it? The top five cloud providers—Amazon, Microsoft, Google, Alibaba, Tencent—host over 70% of global internet traffic. A single undersea cable cut can knock out entire countries. And DNS? Still relies on 13 root server addresses (though they’re anycasted across hundreds of locations). The architecture is distributed. The power isn’t. That’s the uncomfortable truth.
Frequently Asked Questions
Was Jon Postel the inventor of the Internet?
No. The Internet was built by dozens of pioneers—Vint Cerf, Bob Kahn, Leonard Kleinrock, and many others. Postel didn’t invent the protocols. He managed their consistent application. His role was coordination, not creation. But because he maintained the master lists, he had unique influence. Like a conductor, not a composer.
Did Postel have official authority?
Not really. His authority was earned, not granted. For years, he edited the RFC (Request for Comments) series—the technical documents that define how the Internet works. He didn’t enforce rules. He curated consensus. That’s why people listened. It wasn’t his title. It was his track record.
Is IANA still important today?
Yes. IANA functions are now operated by ICANN, but they still manage IP address allocation, protocol parameters, and the DNS root zone. It’s less about power and more about stability. One typo in the root zone could break the web. So the job remains critical—even if the spotlight is gone.
The Bottom Line
Jon Postel didn’t “save” the Internet in one dramatic act. He nurtured it, protected its openness, and when necessary, defended it from capture. His 1998 email wasn’t a power grab. It was a stress test of the system’s values. And the system passed—because people chose to follow him. Today, we rely on institutions, not individuals. Which is safer. But also colder. Less human. I am convinced that we need both: structure and soul. Rules and trust. The next crisis won’t be solved by a lone engineer at a terminal. But maybe, just maybe, it’ll be inspired by one. That’s the legacy. Not glory. Not fame. Just quiet, stubborn integrity. Suffice to say, we could use more of that.