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.
ICANN
The Forged Letter That Moved Sex.com: Kremen v. Cohen and Network Solutions
A forged instruction did not move a physical entity. It changed the authoritative registration record for a domain name—and forced a federal appellate court to ask what, exactly, the registrant controlled.
ICANN
A Domain Name in a Receiver’s Hands: Office Depot v Zuccarini
The judgment was entered in Florida, the debtor lived elsewhere, the registrars were scattered across three countries, and the `.com` registry sat in Northern California. To collect the debt, the Ninth Circuit had to decide where an intangible domain name could be found.
History
Two Queries, Two Servers: Why DNS Needed NSID
A service address can stay the same while the machine answering changes. DNS needed a way to identify the instance behind a particular reply, not merely whichever instance answered the next question. The resulting standard made the association precise while leaving the identity…
History
The Bit That Could Not Keep a Service Running: Why DNS WKS Never Became a Live Directory
Before opening a connection, an early Internet mailer could inspect one bit in DNS and decide whether a server existed. The bit was exact. The world behind it was not.
ICANN
The Four-Hour Transfer Contact That Cannot Reverse the Transfer
The Four-Hour Transfer Contact That Cannot Reverse the Transfer 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. The…
ICANN
The Writ Reached ICANN; the Registry Data Stayed Abroad
The creditors proposed to sell or license operation of `.ir`. A court could reach ICANN in the United States, but an order changing the root-zone pointer would not deliver the foreign registry’s database, secure a competent successor or oblige the world’s networks to follow the…
ICANN
The drafting room behind root advice: who controls the RSSAC Caucus pipeline?
Most RSSAC reports are built in a body far larger than the committee that formally approves them. The current rules make that division visible: experts may propose, research and draft; root server operator representatives keep the gates for admission, scope, amendment and…
ICANN
The security advisers the Board appoints: where SSAC authority stops
Three dates describe the gate. On 25 November 2025, an internal membership committee recommended three candidates. On 10 December, SSAC approved them by consensus. On 25 January 2026, the ICANN Board appointed them. Expertise entered through a committee of incumbents and acquired…
CASE FILE
The 30 Percent Congress Legalised After It Was Collected
For two and a half years, every covered domain registration carried a public-purpose assessment that Congress had not specifically authorised. One month after a judge exposed the defect, Congress made the past lawful “as if” it had acted first.
History
The Name That Chose a Service: How DNS SRV Found Servers
A domain once led clients toward one address and a remembered port. DNS SRV made service location an explicit, bounded choice among hosts.
History
The Alias That Could Not Move Authority: DNS DNAME
DNAME redirects descendant lookups by replacing one suffix. The owner, zone apex and NS delegation stay put even when many queries follow the new subtree.
History
The Name Created by a Question: How DNS Wildcards Stay Bounded
A DNS wildcard can synthesize a name never stored in the zone. Exact nodes, empty non-terminals and delegation still decide when that default may answer.
CASE FILE
The Answer That Won the Race: Kaminsky's DNS Poisoning and the Entropy Behind Trust
The dangerous answer did not need a signature or a privileged route; it only had to resemble one outstanding question closely enough and arrive first. The 2008 DNS crisis turned that narrow acceptance rule into a renewable race—and showed why a patch can buy safety without…
CASE FILE
The Signature That Demanded Every Key: What KeyTrap Revealed About the Cost of Trust
KeyTrap turned a valid-looking DNSSEC workload into a claim on somebody else’s processor, exposing the point at which faithful verification must yield to a locally governed budget.
CASE FILE
The Root That Wasn't Sold: What Symantec's Exit Revealed About Transferable Trust
Symantec could sell its certificate-authority business, but it could not sell a command to keep trusting the old roots. That decision remained inside independently operated clients.
CASE FILE
The Route That Borrowed a Name: What the MyEtherWallet Hijack Revealed About Layered Authority
A route accepted elsewhere let false DNS answers arrive locally, but the 2018 MyEtherWallet attack still had to cross a chain of independent technical vetoes.
ICANN
ICANN’s Alternative-Name Test Stops at Technical Feasibility
ICANN has opened public comment on a model for linking a gTLD to the same string in alternative naming systems. The initial report says the arrangement can be technically safe if one controller and one coherent source of truth govern every copy of the name. That is a demanding…
History
The Number That Became Newer After Zero: How DNS Ordered Versions Without a Clock
At the edge of a 32-bit counter, DNS asks operators to accept an apparent impossibility: zero may be newer than 4,294,967,295. That rule let independent name servers agree on version order without sharing a clock, but only inside a deliberately bounded window.
History
The Zone That Knocked: How DNS NOTIFY and IXFR Cut Staleness
DNS once made every secondary wait before learning its authority was stale. In 1996, NOTIFY delivered the knock and IXFR carried only the edit.
History
The Address You Needed DNS to Find: How Glue Broke the Delegation Loop
A DNS referral can name the server that knows the answer and still leave a resolver unable to reach it. Glue was the small, deliberately non-authoritative exception that let the resolver cross that gap without giving the parent zone control over the child's facts.