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
The Zone Went Dark. The Resolver Made the Outage Louder
When authoritative DNS stops answering, the first failure belongs to the zone. The next thousand queries may belong to the resolver. RFC 9520 draws a narrow but consequential line between the two: silence is not proof that a name does not exist, yet a resolver that has exhausted…
IETF
Ray Bellis and the Proxy That Had to Forward the Unknown
A small gateway often presents itself as a helpful DNS interpreter: one address for the household, one upstream resolver, one place to cache an answer. RFC 5625, authored by Ray Bellis, starts from the more difficult premise. The gateway cannot know what DNS will mean after its…
CASE FILE
The Handshake Succeeded. The DNS Question Was Already Exposed
RFC 9539 lets a recursive resolver encrypt its next hop to an authoritative server without waiting for the server to advertise a new policy or present a verifiable identity. That modest bargain can hide many DNS questions from passive observers. It also creates an unusually…
CASE FILE
The TLS Session Resumed. The DNS Subscription Did Not
DNS Push can make a changing RRset look continuously current by stopping the client’s TTL clock and replacing polling with a server’s promise to send changes. That promise belongs to one accepted subscription on one live DSO session. A resumed TLS channel is cheaper to rebuild…
CASE FILE
The Record Expired. The Resolver Kept It Alive
DNS Serve Stale can preserve service when authorities cannot answer. It can also keep a retired address or denial alive after the publisher's ordinary freshness claim has ended. The difference lies in who owns the exception and whether its evidence survives.
IETF
DNS Serve-Stale Lets the Recursive Resolver Decide When Expired Data Is Better Than Failure
A DNS record reaches the end of its TTL just as every authoritative server becomes unreachable. The old address may still preserve a working service—or it may lead users back to infrastructure the zone owner meant to retire. Serve-stale keeps resolution alive by giving the…
CASE FILE
Two Answers Said NOERROR. Only One Carried the New Zone
RFC 9660 can bind a DNS answer to the zone version that produced it. That makes a mismatch visible without pretending that one version token proves the zone is correct, the fleet has converged or users saw the same path.
CASE FILE
The Service Vanished. Its DNS Lease Did Not
A DNS Update Lease can make stale records expire without a cleanup command. It can also keep an authoritative answer valid long after the advertised service has stopped, because the server—not the requester—sets the operative publication horizon.
CASE FILE
The Catalog Went Empty. The Servers Obeyed
A DNS catalog zone can turn one compact, authenticated change into a new operating perimeter for an entire authoritative fleet. That efficiency is precisely why the catalog must be governed as executable authority rather than treated as a harmless list.
History
The Prefix the Resolver Sent on Someone Else’s Behalf: EDNS Client Subnet
A recursive resolver usually speaks to an authoritative server from its own address. EDNS Client Subnet changed the message: the resolver could send part of a client's network instead, asking the authority to tailor an answer for someone who had not made that upstream query. The…
CASE FILE
The signed chain skipped a delegation that still existed
NSEC3 Opt-Out allows a large parent zone to leave eligible insecure delegations out of its signed hash chain. That omission can be fully valid. It is also why the chain cannot serve as a complete delegation register: the proof authenticates a limited statement about a hash…
IETF
QNAME Minimisation Makes Each DNS Delegation See Only What It Needs
A root server does not need an entire host name to point a resolver toward the next delegation. QNAME minimisation turns that observation into a disclosure rule: reveal the name one boundary at a time, measure fallback, and never confuse less upstream exposure with privacy from…
ICANN
UA Day Built 17 Demonstrations. Production Readiness Needs a Return Visit
On one page of ICANN’s UA Day 2026 report, seventeen rows turn an institutional slogan into working entities. There is an internationalized domain from Kenya and a sample Arabic-script mailbox; another row carries Tifinagh, another Thai, another Telugu. These are not signatures…
History
The Error That Could Explain Itself Without Changing the Answer
Two DNS replies can carry the same `SERVFAIL` result and demand opposite repairs. One may mean that no authoritative server could be reached. The other may mean that a validating resolver received data it was required to distrust. For decades, the wire result hid that difference.…
IETF
An IETF CCG Seat Is Not Title to IANA
On 11 August 2026, the Internet Architecture Board reappointed Tim Wicinski to the Community Coordination Group. He occupies one of three IETF-selected positions in a nine-person body drawn equally from the names, numbers and protocol-parameters communities. The CCG advises the…
CASE FILE
The serial matched. The zone did not
The transfer finished, the file parsed and the SOA serial was exactly the number operations expected. One glue record was nevertheless missing. DNS had long possessed ways to say that a copy was newer and that a transaction came from an approved peer; ZONEMD added a different…
History
The Name That Spent Its Capital Letters: How DNS Turned Case into a Reply Challenge
DNS was built to recognize a name regardless of how its ASCII letters were capitalized. Two decades later, engineers noticed that the discarded distinction could still make a forged reply harder: the name could mean the same thing to the server while carrying a pattern only the…
ICANN
The Domain Name Became the Defendant: Porsche.net and the ACPA's In Rem Route
A lawsuit that began by naming 128 domain names exposed a precise legal control problem: when a registrant cannot be reached through an ordinary personal action, what lets a federal court take authority over the registration itself—and when is it too late to challenge that route?
History
The Reply That Taught a Resolver to Stop Asking
A refusal can end a conversation, or send the question somewhere else. When DNS designers considered a new response code for servers unwilling to provide a conventional ANY answer, unfamiliarity could make resolvers try other authoritative servers. A small, nonempty answer…
North America Cloud Services
The Sheriff Could Not Auction the Registrar's Service: Network Solutions v. Umbro
A portfolio of domain names looked like an asset a sheriff could sell. The Supreme Court of Virginia focused on the missing link: the winning bidder still needed Network Solutions to accept a new registration relationship and keep the names operational.