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.
Story
Five root-server letters, six listed instances: what Panama’s count can tell us
A LACNIC country report names five root-server identities in Panama. Operator site records retrieved later sum to six instances. The figures describe different units and dates; a response-time chart adds a third question: which route and instance did each measurement reach?
Story
APNIC’s Two Root-Key Signals Count Different Things
On 11 October, the DNS root is scheduled to begin using KSK-2024 to sign the zone. APNIC’s latest measurements put two percentages beside that date, but one follows key-tag signals from resolvers while the other tests end systems behind validating resolvers. Their denominators…
History
Who Could Apply for a Top-Level Domain? RFC 920’s First Eligibility List
In October 1984, the first top-level domain list was also a set of admission rules: some names were temporary, others stood for broad categories, and none could enter the tree without an administrator and a route to authorization.
History
The Cache Changed the Destination, Not the Root: AlterNIC’s 1997 InterNIC Redirect
A resolver in one operator’s network returned an AlterNIC address for `www.internic.net`. Its cache record exposed the route the redirect took: additional DNS data had become a local answer. That was evidence of a changed destination at one resolver, not of a new authority taking…
ICANN
The `.mcp` Bid Would Turn Protocol Membership into a Domain Gate
Five applicants now sit in the preliminary `.mcp` contention set. Charleston Road Registry, which trades as Google Registry, proposes that four kinds of connection to the Model Context Protocol qualify someone to register a `.mcp` name. It also gives an unnamed `.MCP Policy…
Leaders
Tina Dam and the Root-Zone Test That Couldn’t Approve a Name
Before an internationalized top-level domain could enter the root, ICANN asked a deliberately narrow question: would encoded labels disturb the servers and resolvers that move DNS queries onward? The laboratory test answered that question within its setup. It could not decide…
ICANN
Five `.agent` Applicants Recur Across ICANN’s Contention Sets
ICANN’s first 2026-round CSV places 13 named applicants in the `.agent` group. Five of those applicant entities appear in at least 11 of the file’s numbered contention sets, giving the crowded name a portfolio dimension that a single application count misses.
History
One IDN Registration Reserved a Package, Not Just a Label: RFC 3743
When a registry accepts a CJK domain label, the visible string may be only one member of a larger administrative family. RFC 3743’s Joint Engineering Team proposed treating selected character variants as one reservation package, while leaving each zone to decide which forms…
ICANN
ICANN’s 56.4% signal is a lead, not an ownership finding
ICANN’s new OCTO report found that 56.4% of a defined 2025 sample of recently registered gTLD names already flagged by reputation lists had at least one technically associated name. The result may help investigators widen a search, but the report did not establish common…
ICANN
UCAS gains a reference rule for multilingual second-level labels
ICANN’s 5 October publication places a script-based ruleset for Unified Canadian Aboriginal Syllabics in its second-level reference collection. The proposal is designed to coexist with French internationalized domain names in one zone, but the reference does not itself approve a…
Europe and Middle East Cloud Services
Genesis Cloud's Peering Story Outlived Its Network: Reading a 10G AI-Cloud Design Against 2026 Routing Reality
Genesis Cloud built a documented, vendor-celebrated interconnection story: a 10 Gbit remote-peering path from Kristiansand to DE-CIX Frankfurt, marketed as the transport backbone of a European AI cloud. In 2026, the independent routing record tells a different story. Separating…
IETF
The Name Was Inactive. It Still Was Not Yours to Register.
The green badge came from a valid registry-information reply. It said the name was not active in DNS. A buyer treated that as a promise that the next create command would work. RFC 5144 never made that promise: the same data model can say that an inactive name is reserved…
IETF
The Answer Was Authoritative. The Resolver Could Still Be Wrong: RFC 9606
RFC 9606 lets a DNS resolver describe selected privacy and filtering capabilities in a standard record. That is a useful signed name tag, not a witness to every query the resolver actually handled.
IETF
The Algorithm Number Was Registered. The Validation Path Was Not: RFC 9558
A DNSSEC algorithm can receive a number, a wire format and a reproducible test vector while remaining absent from the resolver that decides whether a child zone has any supported authentication path at all.
IETF
The Home Kept the Signing Key. Publication Still Moved Outside: RFC 9526
A residential network can author and sign its own public DNS zone without serving a single public query. RFC 9526 turns that apparently paradoxical arrangement into an architecture—and exposes why a valid signature, a successful transfer and a visible answer are three different…
IETF
The Service Advertised Oblivious HTTP. The Key Could Still Name the Client: RFC 9540
RFC 9540 gives clients a standard way to discover an Oblivious HTTP target, its gateway and the gateway’s public-key configuration. It also exposes a harder truth: a privacy service can be honestly advertised, cryptographically valid and operationally successful while a…
History
DNS Could Find an Exact Name. It Could Not Search for What You Meant: RFC 3467
An exact answer can still answer the wrong question. RFC 3467 looked back at the DNS's original bargain and asked what happened when a deterministic network lookup was expected to understand ambiguous human intent.
Global Cloud Services
The per-prefix answer: what each of Datamatix's remaining /24s actually serves
The per-prefix answer: what each of Datamatix's remaining /24s actually serves 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…
IETF
The Server Said Nothing Had Changed. Another Authority Was Already Serving Something Else.
The resolver received a tiny “nothing new” signal and kept the large signed RRset already in its cache. That saved a retrieval. It did not establish that every authoritative server held the same generation—or that the cached entity still represented the operator's current intent.
IETF
The Update Was Accepted. The Parent Had Not Published It Yet.
The child received `NOERROR` from the delegation update receiver and closed its change ticket. Minutes later, an authoritative parent server still returned the previous delegation. Nothing in that constructed sequence contradicts the draft: acceptance means the change should…