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
Documented, Not Established: ICANN's Emergency Registry Backstop and the Terms Nobody Has Read
A failed registry should be a bad day for one company, not for every registrant in a top-level domain. The emergency back-end arrangement that carries that promise is documented. What makes it callable — a live designation, a binding trigger, funded readiness, a tested handoff…
CASE FILE
Netnod's Three Service Lines and the Number That Cannot Be Split
Netnod publishes a peering fabric, a root-server role and a time service. The root system's operators publish one number that can be checked — 2,047 instances — and it cannot be attributed to any of them. Everything else here comes from the operator's own front page, captured on…
CASE FILE
Facebook's servers were running. The way back was broken.
The October 2021 outage was not simply a case of switching the network back on. It also damaged the routes engineers needed to repair it.
ICANN
A DNSSEC comment asks ICANN to align its DS report with RFC 10026
A 16 October submission points to a registry-lock rule that the June assessment describes inconsistently. The distinction matters before ICANN turns its review into requirements for registry operators.
ICANN
A community gTLD must pass a rulebook test before claiming priority
ICANN’s 2026-round process puts two distinct reviews in sequence: first, a proposed community registration policy must be approved for the registry agreement; only then can an eligible application seek priority in a string contention set. A community label starts the route, but…
ICANN
ICANN marks the root KSK transition complete, with two retirement stages still ahead
The root zone began signing with KSK-2024 on 11 October. ICANN’s completion notice is dated four days later, while IANA’s public schedule still gives the previous key a January revocation and a March removal date—and ICANN says it is assessing reports of issues affecting a…
History
A Third Nameserver Was Not a Third Failure Domain: RFC 2182, 1997
Three authoritative DNS names on a zone did not create three independent ways to reach it. In 1997, BCP 16 made location and network topology part of the redundancy decision.
History
Bhutan’s .bt Changed Hands Before the Internet Arrived
Bhutan’s country-code domain was already recorded in the global naming system before the country opened Internet service to its citizens. Its early history was not a simple handoff from one national operator to another: a retrospective describes an initial private arrangement, a…
History
The .hk Registry Changed Hands in Stages: Hong Kong, 2000–2002
Hong Kong’s domain-name handover was not a midnight switch in the Internet’s root. It was a sequence of policy, service and corporate changes: a public consultation, new registration rules, a nonprofit registry, and a transfer of the operating company and its records.
History
Tonga’s .to Records Reached Abroad While Its 64 kbps Link Was Still Planned, 1996–97
A country-code name could be visible to the world before the island had a documented public Internet route of its own. Tonga’s early records show two different infrastructures moving on different clocks: .to nameservers and hosts already operating overseas in April 1996, and a…
History
Uruguay’s .uy Identified Email Before the Internet Link Arrived, 1988–94
In Uruguay, messages could cross borders before the country had a permanent Internet connection. The email route, the national domain and the later academic link marked three different capabilities.
History
DENIC Was Founded in 1996. Karlsruhe Ran .de Until 1999.
The creation of a cooperative did not move a live domain system. DENIC eG had a Frankfurt office in 1997, while technical operation of the German country-code namespace remained with the University of Karlsruhe until a separate handover in 1999.
History
Honduras Reached the Internet by Satellite. A .hn Dispute Split HONDUNet
A June 1995 announcement said a satellite link had connected Honduras to the Internet. A later history dates the link five days later. Between the project plan and that route sat a dispute over who should administer `.hn`—one that paused HONDUNet and sent its organizers to a…
History
A Country Code Became a Registry Product: Tuvalu’s .tv Deal, 1999–2000
In 1999, Tuvalu agreed to let a U.S. company commercialize registrations beneath its country-code top-level domain. Company and government records describe different parts of the arrangement: a global registry business, a government stake and board seat, and cash payments. They…
Story
APNIC’s 70% KSK signal does not count the users at risk
APNIC Labs’ sentinel tests and Verisign’s resolver reports both tracked readiness for the 2026 root KSK rollover, but they sampled different populations from different vantage points. Neither percentage is a headcount of people who could lose DNS service.
ICANN
ICANN’s 14-day gTLD window makes the backup string a one-way choice
An applicant can use the two weeks after Reveal Day to replace a pre-designated gTLD string, but the switch cannot be undone. The replacement may reduce one visible conflict while leaving later routes to contention open.
History
A Root Server Moved to London; the Root Zone Did Not: K-root, 1997
On 19 May 1997, one experimental root server left its temporary home at Network Solutions and was placed at the London Internet Exchange. The change added a new operating location for K-root and a new operator, RIPE NCC. The accompanying record still pointed to the same unique…
History
A Category Became a Suffix: Symbolics and the First .com, 1985
On 15 March 1985, Symbolics.com entered a namespace still being organized for network administration. The significance of that first `.com` is easier to see when it is separated from the website and commerce stories later attached to it: the record named a company inside a…
Leaders
Terry Manderson and the Reverse DNS Split That Needed Operators
A reverse lookup can lose its path before it reaches the PTR record. A resolver must first find the servers for the reverse zone itself. In 2010, Terry Manderson and Joe Abley proposed dedicated server names for IPv4 and IPv6 reverse DNS. Their RFC made separate operation…
History
Nigeria’s .ng Started with One Domain. The Registry Handover Had to Be Learned
In 1995, the first recorded .ng namespace was remarkably small: a RINAF retrospective says its only registered name at the time was `yaba.edu.ng`. Yet the work around that name—registration rules, a WHOIS database, technical operation and eventual succession—already crossed…