Skip to main content

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.

Conceptual illustration of two colleagues reviewing a domain register and handover checklist in a 1990s Nigerian networking office.

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…

Oct 14, 2026
The Key Was Generated in Two Rooms: DNSSEC’s First Root KSK Ceremony, 2010

History

The Key Was Generated in Two Rooms: DNSSEC’s First Root KSK Ceremony, 2010

The signed root zone appeared in July 2010, but the public milestone concealed a more exacting sequence. A key was generated, protected, moved and accepted across two facilities before the root began carrying DNSSEC signatures. The interval between those steps shows what a…

Oct 14, 2026
Abstract root-signing key transition connected to independent recursive resolvers with distinct local trust-anchor states and separate user-query paths.

ICANN

The root key switched on schedule. Can operators prove their resolvers trusted it?

At 14:00 UTC on 11 October, the DNS root zone began using KSK-2024 to sign its key set. That establishes a public control-plane milestone. It does not establish what every recursive resolver had stored, whether its automatic update completed, or what any particular user…

Oct 14, 2026
Conceptual illustration of a Unix administrator maintaining local domain records while queries reach other independently managed domains.

History

BIND Put DNS Inside 4.3BSD

A distributed name service became a practical part of Unix administration when Berkeley’s BIND arrived as software that operators could configure, run and maintain with the rest of their system.

Oct 14, 2026
Абстрактный корень DNS соединяет разрозненные фрагменты; янтарная ветвь пространства имён продолжается через разлом.

History

The Union Dissolved. .su Stayed in the DNS Root

When the Soviet Union disappeared, its country-code domain did not vanish with it. The history of .su is a record of several clocks running at once: a root-zone delegation, a new Russian namespace, local registration rules, and the names that organizations still needed to…

Oct 14, 2026
An abstract DNS hierarchy with locks beside a review checklist.

ICANN

ICANN’s DNSSEC fast track faces a lock test

ICANN’s assessment and RFC 10026 give registry locks different effects. The difference now sits inside a public review intended to underpin faster registry approvals.

Oct 14, 2026
Каллиграфическую метку на письме урду проверяют, кодируют и делегируют в иерархию корня DNS.

History

The Urdu Name Passed in 2011. .پاکستان Reached the Root in 2017

Pakistan’s Urdu-language name entered the DNS root through two distinct stages: review of the script label, then delegation of a manager able to operate it. The record makes clear why “approved” and “delegated” were not the same milestone.

Oct 14, 2026
An analyst examines one flagged domain among a network of associated names.

ICANN

Linked domains are leads, not verdicts: ICANN’s proposed DNS-abuse checks

ICANN’s proposed associated-domain checks would move abuse review from one name at a time to evidence about related names held by the same registrar. Their legitimacy will turn on a boundary the draft already recognizes: a signal that links domains can justify an inquiry, but it…

Oct 14, 2026
Концептуальная иллюстрация переноса имён интернет-инфраструктуры из .int в .arpa и отдельной проверки старых делегирований.

History

The Infrastructure Names Stayed in .int for 20 Years After .arpa Took Over

A namespace can have a new home long before its old records disappear. The history of .int’s infrastructure names shows why those are separate jobs.

Oct 14, 2026
Conceptual illustration of two branching address directories linked through DNS above a separate mail-delivery path through a gateway; no worldwide deployment is depicted.

History

The PX Record Mapped Addresses, Not Mail: RFC 1664’s Experimental Proposal

An Internet mail gateway needed to translate between two address systems; it did not need DNS to deliver the message. RFC 1664 proposed a way to distribute those mappings, while explicitly leaving SMTP delivery to MX and the gateway.

Oct 13, 2026
Conceptual illustration of a blank domain-registration desk and six folders, with abstract servers beyond an ocean horizon; no real Tanzanian site or route is shown.

History

Tanzania’s .tz Registry Ran Before the Country Had a Full-Time Internet Link

The .tz namespace became operational in 1994 while Tanzania still lacked a full-time Internet connection. The registry could function because domain administration, DNS hosting, mail relay and live IP connectivity were separate layers.

Oct 13, 2026
Conceptual editorial illustration of a child-zone operator sending a signed DNSSEC record to a separate parent-zone registry for validation before a DS update.

ICANN

ICANN Opens the DNSSEC DS Automation Safety Case to Public Review

ICANN has opened a six-week review of an external security assessment that could shape a later Fast Track route for registry operators. The report’s favorable conclusion is conditional; ICANN’s own determination and any contractual change still lie ahead.

Oct 13, 2026
A root-zone cabinet connects an aging namespace to two successor registries through a temporary bridge, with email and account services in the background.

History

Why .YU Stayed in the DNS Root Until 2010

The ISO code changed before the old domain stopped serving people. Between those dates, a temporary registry, replacement namespaces and a staged migration had to bridge the distance between administrative identity and addresses already embedded in daily use.

Oct 13, 2026
Paper domain-request cards and a handwritten ledger give way to an early registry terminal and unbranded name servers, illustrating a shift from volunteer processing to central operations.

History

Who Could Add a Name? Britain’s Manual .uk Registry, 1985–96

Before Nominet, adding a British domain name depended on a volunteer-run naming process. The 1996 handover put the growing register, its operating rules and its member structure into a dedicated institution.

Oct 13, 2026
Sam Weiler in an editorial portrait against an abstract DNSSEC trust-path background.

Leaders

Sam Weiler and the DNSSEC Trust Path Outside the Parent Zone

DNSSEC Lookaside Validation gave a signed child zone another way to reach a validating resolver when its parent could not publish a usable DS record. The detour still depended on a second, locally configured trust anchor. Sam Weiler’s RFC 5074 describes that bargain; the later…

Oct 12, 2026
Conceptual reconstruction of Korean Internet registration records moving from a university lab toward a national agency archive.

History

From KAIST to the NCA: KRNIC’s Move and Independence

Korea’s early Internet registry changed institutional homes before it became an independent foundation. A September 1994 meeting record captures the handoff in one line—and in a changed nameserver address.

Oct 12, 2026
A remote island links to three distinct scenes: a petition file, a review desk and a separate server cabinet.

History

The Petition Was Not the Transfer: IANA’s 2000 .pn Report

Between 1997 and 2000, Pitcairn’s residents asked for a change in who managed .pn. IANA recommended redelegation; the U.S. Government later implemented the root-zone change.

Oct 11, 2026
A source server distributes matching zone copies to three root servers; a resolver queries one server on a separate path.

History

Postel’s 1998 Root Test Targeted Zone Transfers, Not DNS Queries

In January 1998, Jon Postel asked root-server operators to obtain a copy of the root zone from an IANA server at USC/ISI. His message was about how servers received that copy. It said the data would match the version already available from NSI’s A-root and that the existing rules…

Oct 11, 2026
An amber key-shaped signal crosses dark server racks while a pale legacy-key trace fades below it.

Story

Root DNSKEY Answers Now Show KSK-2024’s Signature

At 15:32 UTC on 11 October, four direct root-server queries returned a DNSKEY signature tagged 38696. A sample three hours earlier still showed 20326; the same four names returned 38696 again at about 16:09 UTC. IANA’s cache-revalidated page then listed KSK-2024 as active. These…

Oct 11, 2026
Three university workstations linked by telephone lines sit above a branching index-card tree, illustrating JUNET names before DNS.

History

JUNET’s Name Tree Came Before DNS—and Survived the Move to .jp

Before Japan’s academic networks used TCP/IP and DNS, JUNET made hierarchical email names work over UUCP and telephone lines. The convention gave volunteers a way to keep organization names legible as the network grew—and a structure that could be carried into `.jp` when a wider…

Oct 11, 2026