By Cliff Potts, CSO, and Editor-in-Chief of WPS News

Baybay City, Leyte, Philippines — March 24, 2026, 17:35 PHST

The concentration of informational power on the modern internet is not immutable. It did not arise from technical necessity, and it does not require a wholesale reinvention of the network to correct. The mechanisms that enable control are discrete, identifiable, and correctable.

This essay advances a single claim: we can fix the internet, and this is how—by addressing control at specific layers rather than treating the system as irreparably broken.

What DNS Actually Does

The Domain Name System exists to translate human-readable domain names into numerical IP addresses. Functionally, it is a directory service. When a user enters a web address, DNS answers a narrow and specific question: where on the network is this resource located?

DNS does not evaluate content. It does not assess quality, legitimacy, or importance. It does not rank information or determine relevance. Its role is locational, not editorial.

That simplicity makes DNS easy to overlook.

Resolution as a Structural Gate

Although DNS does not judge content, it determines whether content can be reached efficiently, reliably, or at all. At scale, resolution affects latency, availability, and perceived trustworthiness. These factors shape user behavior long before search or ranking systems come into play.

When DNS resolution is handled by a small number of large operators, resolution becomes a structural gate rather than a neutral directory. Decisions about blocking, filtering, or redirection can be applied upstream of discovery systems, often without user visibility.

Control introduced at this layer propagates silently.

Centralization by Convenience

DNS was designed to be distributed. In practice, convenience has driven consolidation. Large public resolvers offer speed, reliability, and ease of configuration. Individuals, organizations, and even governments adopt them because they work well and require little maintenance.

Over time, this convenience creates dependency. Resolution data concentrates. Patterns of access become observable. The ability to influence resolution outcomes accumulates in a small number of entities.

Centralization emerges without explicit mandate.

Why DNS Matters for Discovery

All discovery systems operate downstream of DNS. Search engines, indexes, crawlers, and ranking systems assume that resolution is neutral and broadly available. When resolution itself becomes centralized, downstream systems inherit that concentration automatically.

Content that resolves slowly, inconsistently, or unreliably loses visibility regardless of its quality or relevance. This effect occurs before any ranking algorithm is applied.

DNS is not the only chokepoint—but it is the first.

Corrective Measures at the Resolution Layer

Undoing concentration at the DNS layer does not require abandoning DNS or replacing core internet protocols. It requires restoring plurality.

Corrective measures include:

  • diversification of DNS resolvers at institutional and regional levels
  • separation of resolution services from analytics and profiling
  • support for local, sector-specific, or public-interest resolvers
  • policy constraints limiting resolution-based intervention

These changes do not alter TCP/IP. They alter who performs resolution and under what conditions.

Upstream Corrections Have Downstream Effects

Because DNS sits upstream of discovery and ranking, corrections applied at this layer propagate downward. Reducing concentration here weakens the leverage available to centralized platforms further along the stack.

DNS reform alone does not fix the internet.
But without it, downstream fixes remain fragile.

If discovery is to be pluralistic, resolution must be plural first.

This essay will be archived in the WPS News Monthly Archive, available through Amazon.

This work may be cited freely. Licensing or implementation for commercial or institutional use requires prior arrangement.

References

Mockapetris, P. (1987). Domain names—concepts and facilities. RFC 1034. Internet Engineering Task Force.

Mockapetris, P. (1987). Domain names—implementation and specification. RFC 1035. Internet Engineering Task Force.

Mueller, M. (2017). Will the Internet fragment? Sovereignty, globalization, and cyberspace. Polity Press.

Deibert, R. (2015). Black code: Surveillance, privacy, and the dark side of the Internet. Signal.

Discover more from WPS News

Subscribe to get the latest posts sent to your email.