Topic
DNS Delegation Power
Within the Topic facet, DNS Delegation Power topic intelligence connects articles that share a specific subject, signal focus, or monitoring theme. The page gives readers a richer path through related reporting, source evidence, market actors, and infrastructure implications, with enough context to understand why the topic matters across company movements, governance decisions, regional exposure, and operational risk. Readers can compare recurring signals, affected organisations, public evidence, market context, service continuity, procurement, competition, compliance, and strategic planning questions behind the subject instead of stopping at a thin list of matching articles. It explains what the topic covers, which infrastructure actors or policies are involved, what evidence supports the coverage, and why the subject may matter for operators, customers, investors, and policy readers.
CASE FILE
The .ECO Community That Became a Registry Right
Big Room’s 14-point Community Priority Evaluation did not establish ownership of environmentalism or place .ECO in the DNS root. It gave one community-based application priority inside a four-way contention set. Narrow review left that score intact; a later registry agreement and…
CASE FILE
How Consensus Advice Held .AMAZON for Five Years
In the .AMAZON dispute, governments did not own the root-zone switch and an independent review panel did not acquire it. The decisive power moved through presumptions, reasons, application status, contract terms and finally delegation—showing how consensus can stop a namespace…
CASE FILE
Why Google Could Not Keep .SEARCH Closed
Google’s registry subsidiary applied to reserve a generic namespace for its own corporate group at a time when ICANN’s published rulebook did not expressly forbid that model. The application exposed a policy omission, and the decisive response came not from public comment…
North America National Telecom
C-Root's 2024 Stale Zone Made Publication Freshness a Root-Server Accountability Test
C-Root kept answering DNS queries while serving an old root-zone view for several days. The incident showed why root-service accountability must measure the freshness of authoritative state, not only whether a server responds.
Europe and Middle East Institutional
The .RU 2024 DNSSEC Rollover Failure Made Zone-Signing Verification an Accountability Test
A planned .RU DNSSEC zone-signing-key rollover in January 2024 exposed a narrow but serious accountability problem: redundant authoritative DNS cannot protect users when the shared signed-zone artifact is internally inconsistent.
Europe and Middle East Institutional
DENIC's 2026 .de DNSSEC Failure Made Signing-System Parity an Accountability Test
A routine .de ZSK rollover showed that geographic and hardware redundancy cannot preserve DNS availability when systems distributing a shared zone do not share the same valid cryptographic state.
Leaders
Bevil Wooding and the Operational Work Behind Caribbean Internet Resilience
Bevil Wooding's public record connects Internet exchange development, a regional network operator community, post-hurricane infrastructure analysis, and a bounded role in root DNSSEC recovery. Those records show how continuity depends on distinct people and institutions keeping…
Global Cloud Services
GoDaddy's 2012 DNS Outage Made Router-Table Change Control an Accountability Test
GoDaddy's 10 September 2012 outage showed how an operator can retain valid domain records while failures in running network state make names, websites, email and the operator's own support systems unreachable. The accountability question is not whether one record or one backup…
Global Cloud Services
Turkey's 2014 Public DNS Interception Made Resolver Routing an Accountability Test
The 2014 interception of public resolver addresses inside Turkish networks showed why a configured DNS destination is not proof of the route, answering system, response integrity, or restoration state that users actually received.
Global Institutional
The 2002 Root DNS Attack Made Distributed Service Resilience an Accountability Test
The October 2002 attack against the DNS root server system showed why an accurate record of authority is not an availability guarantee. Accountability rests on reachable authoritative service, route and capacity diversity, resolver behavior, traffic controls, measurement…
Global Cloud Services
UltraDNS's 2014 DDoS Attack Made Authoritative DNS Continuity an Accountability Test
The 30 April 2014 disruption of Neustar's UltraDNS service showed why authoritative DNS must be treated as running network infrastructure rather than a static entry in a configuration file. The accountability question is whether the provider, its carriers and its customers could…
Global Cloud Services
Azure's 2021 DNS Cache Defect Made Retry Amplification an Accountability Test
Azure DNS did not need every client request to be hostile for its 1 April 2021 outage to grow. Microsoft said an anomalous global query surge exposed a code defect that reduced the efficiency of DNS Edge caches. As the service overloaded, ordinary DNS clients retried unanswered…
Global Cloud Services
The 2019 Route 53 DDoS Made DNS Mitigation Coordination an Accountability Test
On 22 October 2019, Amazon Route 53 was hit by a distributed denial-of-service attack. The attack impaired resolution of some AWS names, but the most revealing part of the public record was not that a large authoritative DNS service received hostile traffic. It was that defenses…
Global Cloud Services
The 2018 Route 53 Hijack Made BGP-to-DNS Trust an Accountability Test
The 2018 Route 53 Hijack Made BGP-to-DNS Trust an Accountability Test intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow.…
Leaders
Robert Elz and the .au Stewardship Handoff From Personal Trust to Accountable Registry Operations
Robert Elz's documented role in .au is a study in what responsible technical stewardship looks like when a public namespace outgrows dependence on one trusted person. The lasting achievement was not simply holding responsibility, but participating in a process through which that…
CASE FILE
The .se Incident: When Registry Zone Publication Defeated DNS Redundancy
A malformed country-code top-level-domain zone showed why resilient DNS servers cannot compensate for a shared publication failure, and why recovery must restore semantic and cryptographic validity together.
Leaders
Hugo Salgado and the DNS Operations Record Behind .CL
The public record around Hugo Salgado Hernandez is most revealing when read through the routine disciplines of DNS operation: automating carefully bounded changes, learning with a regional technical community, and making distributed authoritative systems easier to diagnose.
NANOG
A NANOG correction moves domain takedown planning above the registrar
A new operator-thread correction shows why a registrar-only recovery plan can stop one layer too low. In the reported `.com` lock, the server-side control sat with Verisign as registry operator, while the registrar remained an escalation channel rather than the actor able to…
Global Institutional Trends
Gaurab Raj Upadhaya and the Bounded Custody of the Root Key
A small metal key helps explain a large institutional achievement: how the root of DNSSEC can depend on a volunteer's presence while denying that volunteer the power to act alone.
Global Cloud Services
One Git Push from Bucharest: Anverino Software and the Hard Economics of LuaDNS
LuaDNS turns authoritative DNS into something a small engineering team can review, script and deploy like software, but its unusually open control surface also exposes the central procurement question around a lean infrastructure operator: whether verifiable routing, disciplined…