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.
Asia-Pacific Institutional
PANDI's .id registry runs on AS132647 while AS56088 is absent from public BGP
PANDI's .id registry runs on AS132647 while AS56088 is absent from public BGP 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…
Leaders
Anand Buddhdev and the Discipline Behind DNS Reliability
Anand Buddhdev's public record is not a story about charisma, invention, or solitary control. It is a profile in operational stewardship: the slow work of keeping DNS services measurable, retiring inherited services without abandoning users, expanding root and authoritative…
Story
DNSSEC Key Rollover and the Governance of Irreversible Mistakes
A cryptographic key can be generated again. Trust cannot always be recalled. Once a new trust anchor has reached resolvers, an old key has been revoked, cached records have diverged or dependent operators have acted on a signed state, the administrator is no longer editing one…
Leaders
Jorge Cano and the Registry Work That Makes Names Resolve
Jorge Cano Puente’s public record is not the familiar profile of a telecom executive, founder, or regulator. It is the quieter profile of a registry systems engineer whose work sits inside the machinery that lets domains be registered, authenticated, queried, delegated, and…
History
Geneva 2003: The Compromise That Deferred the Authority Question
The first phase of the World Summit on the Information Society did not decide who held final authority over the Internet. It made a different bargain. Governments received an express statement that policy authority over Internet-related public policy was a sovereign right of…
Leaders
David Ulevitch and the Market for Resolver Trust
David Ulevitch's career is a study in how a quiet layer of internet operations can become a business, then a security platform, then an investment thesis. From EveryDNS and OpenDNS through Cisco Security and Andreessen Horowitz's American Dynamism practice, the public record…
Leaders
Dave McBreen and the registrar layer beneath Identity Digital's consumer surface
Dave McBreen's public record is not the story of a loud founder remaking the domain market from a podium. It is the quieter case of an operator who entered Name.com when the registrar was still young, worked close to its software and infrastructure, and later became the executive…
Leaders
Gaurab Raj Upadhaya and the bounded authority of Nepal's internet institutions
Gaurab Raj Upadhaya's public record is not a simple current-title biography. It is a way to see how Nepal-facing internet exchange work, operator forums, research-network service, global anycast DNS operations, APNIC governance and root DNSSEC trust can turn individual technical…
Story
The Parent Zone and the Power to Refuse a Child
A reverse-DNS operator can serve a technically perfect child zone and still remain invisible if the parent will not publish its delegation. In the hierarchy beneath `in-addr.arpa` and `ip6.arpa`, refusal can occur at more than one boundary, for more than one reason, under more…
Story
Reverse DNS as a Quiet Sanction
An address block can remain routed, its servers can keep answering and its forward names can still resolve, yet a small deletion higher in the reverse-DNS tree can make its mail look untrustworthy and its network harder to operate. That is why reverse delegation should not be…
Europe and Middle East Institutional
The infrastructure downside at IE Domain Registry CLG
IE Domain Registry CLG carries the economic downside of Ireland's national domain infrastructure because the visible .ie footprint is only the demand side of a heavier bargain: the company must keep a critical registry, DNS service, policy process and registrar channel resilient…
Leaders
Lars-Johan Liman and the operating discipline behind I-root
Lars-Johan Liman's public record shows how a co-founder of a Swedish internet infrastructure institution can matter without turning root-server operations, DNS governance or Netnod's institutional work into a personal-command story.
Leaders
Ondřej Filip and the public-software discipline behind Czech internet governance
Ondřej Filip's public record is not just a list of internet-governance titles. It is a way to see how a national domain registry can turn software, routing, security and institutional trust into a durable public operating system without pretending that one executive controls the…
History
Vint Cerf after TCP/IP: the authority that could not govern the internet alone
Vint Cerf's durable influence is not simply that he helped design TCP/IP. It is that, after the protocol suite became infrastructure, his authority had to move through institutions, open standards, identifier coordination, public advocacy, and corporate stewardship. That later…
Global Cloud Services
Dyn made DNS dependency a revenue-continuity accountability problem
The October 2016 attacks against Dyn showed that a business can keep its servers running and still lose public reachability when DNS resolution fails upstream; the accountability question is who had practical control over provider concentration, DDoS absorption, failover design…
ICANN
ICANN made the DNSSEC root key rollover a readiness-evidence problem
The first DNSSEC root Key Signing Key rollover was not a story about a global outage. It was a story about how a global maintenance event should prove readiness before it touches the trust anchor that validating resolvers depend on. ICANN's postponement in 2017 and completion in…
Global Cloud Services
Dyn made authoritative DNS resilience a customer-failover accountability test
The 2016 attacks against Dyn showed that a service can be technically healthy and still disappear from users if authoritative DNS fails. The accountability question is not only whether Dyn absorbed the DDoS, but whether customers had designed, tested, and governed failover well…
History
Dyn made managed DNS a revenue-continuity accountability boundary
The 2016 Dyn attack did not take down the internet. It did something narrower and more costly for dependent services: it made revenue, login, payment, media, support, and public-information flows unreachable because a shared authoritative DNS provider was overwhelmed. The…
History
Let's Encrypt made root expiration a certificate-trust accountability boundary
The DST Root CA X3 expiration was not a classic outage caused by one broken server. It was a trust-boundary incident in which certificates, cross-signs, operating-system trust stores, old clients, hosting panels, libraries, and subscriber choices interacted in ways that made some…
History
DigiNotar made certificate-authority failure an operational-harm control test
DigiNotar's 2011 compromise was not only a story about fraudulent certificates. It was a public-trust failure in which one certificate authority's weak controls, delayed notice, government dependency, browser distrust, and emergency migration decisions determined whether users…