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
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.
ICANN
ICANN Has an Application Count, Not Yet a String Count
ICANN closed its 2026 new-gTLD window with more than 1,600 primary applications and more than 1,100 replacement-string options. Those figures describe the queue at submission, not the final set of names that will proceed through evaluation.
History
Two Kinds of Nothing: How DNS Learned to Separate NXDOMAIN from NODATA
An empty DNS answer can conceal two opposite realities: the requested name may be absent altogether, or it may be alive and carrying every record except the one requested. The Internet had to make that difference portable, cacheable and temporary before saving queries could stop…
History
The Error That Learned to Expire: How DNS Cached What Did Not Exist
The expensive DNS question is not always the one with a large answer. It may be the miss that thousands of resolvers repeat because nothing can be stored. Negative caching gave absence a scope, evidence and an expiry time—then forced operators to accept that a newly created name…
History
The Mail Address That Outlived Its Server: How MX Records Separated Identity from Delivery
An email address looks like a destination. In the early Internet, it often was: a mailer could take the domain after `@`, open SMTP to the machine with that name and hope the mailbox lived there. In January 1986, RFC 974 described why that assumption had stopped scaling—and how…
Story
RIPE NCC Split ENUM's Future From 23 Troubled Delegations
A draft prepared for September's ITU-T Study Group 2 meeting makes a careful retreat from a system-wide question. RIPE NCC now says Public ENUM should continue while 17 non-operational and six partly faulty delegations are handled as individual registry cases. The change is less…
CASE FILE
Mozilla’s Hidden Security Boundary: How the Public Suffix List Becomes Running Code
Mozilla began the Public Suffix List, and Firefox still turns a version of it into browser behaviour. The DNS can tell software that `whatwg.github.io` exists beneath `github.io`, but not whether those names belong to one organisation or mutually untrusting tenants. This article…
ICANN
ICANN’s .juniper successor comment window reaches its final day
Interested parties have until 23:59 UTC on 19 August to respond to ICANN’s preliminary view that Juniper Networks’ brand top-level domain does not need a successor registry. The contract is on an exit path, but the namespace is still listed in the root-zone system.
IETF
The Public ENUM Response Date Has Passed. The Decision Has Not.
An ITU-T consultation on possible closure of E.164 country-code delegations in `e164.arpa` named 15 August 2026 for Member State responses. The public record still does not state an outcome.
ICANN
IANA marks Root KSK Ceremony 62 complete — what the public record actually says
IANA now labels Root KSK Ceremony 62 complete. Its public record identifies a 12 August operation for 2026Q4 ZSK signing and retirement of two HSMs; it does not itself publish an independent audit conclusion.
ICANN
ICANN’s 2026 application window has closed; registry operations now become the practical test
At 23:59 UTC on 12 August, ICANN’s 2026 new-gTLD application window and its Registry Service Provider evaluation window both closed. The deadline does not decide which labels will reach the DNS; it moves attention to the operating capability that will have to support any…
ICANN
ICANN leadership needs measurable institutional priorities
A new chief executive can set pace and management discipline. ICANN’s legitimacy still depends on processes that no single leader controls.
Story
AFRINIC ended 2012 with 49 DS records from only two members
AFRINIC’s year-end disclosure captured real use of a new member-facing service: 49 DS records associated with 13 domains, supplied by two members. The exactness of those numbers is valuable, but it is not an adoption rate. Without a count of eligible members or domains, signed…
Story
AFRINIC completed the parent trust chain for its signed reverse zones
On 10 May 2012, IANA’s publication of DS records in the two parent reverse zones changed what validating resolvers could verify about AFRINIC-signed reverse DNS. The significance lay in matching keys, delegation state and a reversible operating procedure—not in any enlargement of…
Story
No Reverse Unless Assigned: Draft 1 Put a Database Error in the DNS Decision Path
On 10 April 2012, Tim McGinnis submitted the first “No Reverse Unless Assigned” proposal, asking AFRINIC to condition a new reverse-DNS delegation on a registered assignment or sub-allocation. The draft confronted a genuine weakness in public network records, but it also exposed…
Story
Nine Zones, One Open Link: What AFRINIC’s DNSSEC Phase 2 Actually Changed
On 3 May 2012, AFRINIC began distributing signed versions of nine IANA-delegated reverse-DNS zones—six for IPv4 and three for IPv6—while deliberately leaving the parent DS connection and the publication of members’ DS records for a later phase. That distinction was not a…
Leaders
Joe Abley and the Work of Making Distributed DNS Visible
One Internet address does not always lead to one machine. A service can place machines in many cities, connect them through different networks, and make all of them reachable through the same address. The arrangement can make a service easier to reach from many places, but it…