The two organizations are ICANN (the Internet Corporation for Assigned Names and Numbers) and Verisign. ICANN sets global policy for the top-level domain name space and coordinates the root server system; Verisign operates two of the thirteen named root server identities, runs the authoritative root zone publication service under contract to ICANN, and maintains the .com and .net registries.
That split confuses people because both names appear in the same documents. One governs, the other operates. Keep that division in mind and the rest of the picture β root zone file, root server letters, IANA functions, the cooperative agreement β falls into place.
The Three-Layer Model: Policy, Protocol Parameters, and Root Operations
Start with the layer that answers the exam question directly. ICANN's board holds the policy mandate for generic top-level domains: it approves new gTLD rounds, delegates country-code domains through the IANA function, and sets the rules registries and registrars must follow under the Registrar Accreditation Agreement. The IANA department inside ICANN also administers the protocol parameter registries that give DNS its numeric constants.
The second layer is operational. Verisign does not decide whether a new top-level domain may exist. It executes the changes once approved, generating the root zone file that every resolver in the world relies on. Verisign publishes that file through its distribution service, and the file's serial number increments each time the zone changes, which currently happens several times a day.
The third layer is physical. Thirteen named root server identities exist, labeled A through M. Verisign operates A and J. The other eleven are distributed among NASA Ames, the University of Maryland, the U.S. Army Research Lab, Netnod in Sweden, RIPE NCC in the Netherlands, ICANN itself, and others β a deliberate geographic spread so no single failure or jurisdiction takes the whole root offline.
Layer one sets policy, layer two publishes data, layer three answers queries. Confusion arises because ICANN sits in layers one and three at once, operating B and L root identities while also holding the policy pen.
ICANN's Actual Powers Over the Top-Level Domain Space
ICANN is a California nonprofit public benefit corporation incorporated in 1998, succeeding the IANA function originally run by Jon Postel at USC's Information Sciences Institute. Its board of directors approves every delegation and redelegation of a country-code top-level domain. That power is real but procedural: the board acts on IANA's assessment following the applicant's local support documentation, not on its own preference.
For generic domains, ICANN runs the new gTLD application rounds and enforces the contracts. A registry that misses its service-level requirements faces contractual remedies, up to termination of its registry agreement. ICANN's compliance team publishes monthly breach notices, and the numbers are public β useful evidence that the policy layer has teeth.
The IANA naming function is where the two organizations touch daily. IANA receives a change request, verifies it against the relevant policy, asks Verisign to execute it in the root zone, and Verisign publishes the result. In 2016 the U.S. Commerce Department's National Telecommunications and Information Administration let its stewardship contract with ICANN expire, moving the IANA function fully into ICANN's accountability framework. NTIA retained a separate cooperative agreement with Verisign covering root zone maintenance.
Here is the detail most explainers skip: ICANN's bylaws require a root zone change to go through a documented review clock. Separately, NTIA's cooperative agreement with Verisign obliges Verisign to verify that any root zone change has ICANN's authorization before publishing. Two independent checks on the same file.
Verisign's Operational Role: Root Zone File and Two Root Identities
Verisign is the company most people know for .com. Its role in the root system is less familiar and more consequential. Under the cooperative agreement with NTIA β originally signed in 1998 and amended repeatedly β Verisign operates the authoritative root zone publication service. Every time a top-level domain is added, removed, or has its name servers changed, Verisign regenerates the zone and pushes it to the root server operators.
The zone file is small in human terms and enormous in consequence. It holds entries for every top-level domain in the root: generic domains, sponsored domains, country-code domains, and the infrastructure domains. Each entry maps a name to a set of NS records. A single malformed delegation propagates to every resolver that refreshes from the root.
Verisign's root server identities are A, at 198.41.0.4, and J, at 192.58.128.30. Both run anycast, meaning the same address is announced from many physical locations worldwide. Verisign has published that the A and J identities answer a substantial share of global root queries, a figure that shifts as anycast deployments expand β treat any specific percentage as a dated snapshot and confirm via Verisign's published root server statistics.
There is one crucial correction here. Verisign does not own the root zone. It publishes it under contract, following ICANN's authorization and NTIA's oversight conditions. If the contract ended tomorrow, the operational duty would be reassigned β the data itself is a public trust, not corporate property.
How a Single Root Zone Change Travels From Request to Live Answer
This sequence is where the policy-operations split becomes concrete. Follow one hypothetical delegation through the system.
1: A prospective country-code manager submits a request to IANA, including documentation of local community support and the proposed name servers. 2: IANA reviews the request against the relevant policy framework and, where the country has an established process, confirms support from the recognized local body. 3: ICANN's board or its delegated authority approves the delegation. 4: IANA instructs Verisign to add the delegation to the root zone, supplying the NS records. 5: Verisign regenerates the root zone, increments the serial number, and publishes the new file. 6: Root server operators refresh from the distribution service; the change typically appears across all thirteen identities within minutes. 7: Resolvers worldwide pick up the new delegation on their next root refresh, governed by the TTL on the root zone records.
Failure handling matters more than the happy path. If a name server listed in the delegation is unreachable at verification time, the request stalls at step four; Verisign's technical checks reject a delegation whose servers do not answer authoritatively. If the published zone contains an error, the recovery path runs backward: IANA issues a correction request, Verisign republishes, and operators refresh again. The serial number is the audit trail.
The Thirteen Root Server Identities and Who Actually Runs Each
ICANN coordinates the system; it does not run all of it. The operator list is a good test of whether someone actually understands the structure.
| Letter | Operator | Notes |
|---|---|---|
| A | Verisign | Anycast, global |
| B | USC Information Sciences Institute | Historical first root server |
| C | Cogent Communications | Anycast |
| D | University of Maryland | Anycast |
| E | NASA Ames Research Center | Anycast |
| F | Internet Systems Consortium | Anycast |
| G | U.S. Department of Defense | Anycast |
| H | U.S. Army Research Lab | Anycast |
| I | Netnod | Sweden |
| J | Verisign | Anycast, global |
| K | RIPE NCC | Netherlands |
| L | ICANN | Anycast |
| M | WIDE Project | Japan |
The table shows the real distribution. Verisign is the only organization operating two identities, and ICANN operates one. That overlap is why the two-organization answer to the original question is correct but incomplete: eleven other operators carry the traffic.
Resilience comes from two design choices. Anycast means a single letter identity can be answered from dozens of sites, so a failure at one site reroutes to another. Geographic spread means no single national jurisdiction controls the whole set β a point raised repeatedly during the debates over root server localization in the 2000s.
Why the Answer Is Often Given as Two Organizations, Not One
The question appears in networking exams and interview loops because the "two organizations" framing matches the contractual reality. ICANN holds the policy and coordination mandate. Verisign holds the operational contract for the root zone publication service and runs the .com and .net registries. If you must name two, those are the two.
But the framing has a known weakness. NTIA, part of the U.S. Department of Commerce, remains a party to the cooperative agreement with Verisign and must approve major changes to the root zone maintenance arrangements. Before 2016, NTIA also held the IANA stewardship contract with ICANN. Someone who answers "ICANN and Verisign" without mentioning the historical U.S. government role is giving a current answer, not a complete history.
A second nuance: the root server operators are not formally subordinate to ICANN. They participate through the Root Server System Advisory Committee, which advises the ICANN board. Operators volunteer their service. ICANN coordinates; operators comply with technical standards rather than direct orders.
So the practical answer for an exam is ICANN and Verisign. For a policy discussion, the answer is ICANN, Verisign, NTIA's residual oversight, and the twelve other root operators whose cooperation makes the system work.
The Commonly Confused Terms: Root Zone, Root Servers, and the Root Domain
Three terms get used interchangeably and should not be. The root zone is the data file: the list of top-level domain delegations and their name servers. The root servers are the machines and anycast sites that answer queries about that data. The root domain is the abstract namespace level β the "." at the end of a fully qualified domain name.
A misuse worth flagging: people say "Verisign controls the internet's root servers." Verisign operates two of thirteen identities and publishes the zone. It controls neither the servers it does not run nor the policy that shapes the zone.
Another misuse: "ICANN owns the root zone." ICANN authorizes changes and coordinates the system. The zone is maintained operationally by Verisign under contract, with NTIA's cooperative agreement conditions in force. Ownership language obscures a deliberately distributed trust model.
The origin of the thirteen-server number is worth knowing too. Early designs in the 1980s had fewer root servers; the current letter scheme grew as the network expanded. The thirteen-address limit is a UDP packet-size constraint from the original DNS design, not a technical ceiling on physical machines β which is precisely why anycast allows hundreds of physical servers behind thirteen addresses.
Worked Example: What Happens When a ccTLD Redelegation Goes Wrong
A redelegation is the trickiest routine operation in the system. Suppose a country's ccTLD manager loses local support, and a competing organization seeks the delegation. The request arrives at IANA with documentation. IANA assesses it against the country's framework and, where no framework exists, uses its own procedures.
Now introduce the failure. The outgoing manager refuses to hand over the zone data, or operates name servers that the new manager cannot take control of. Verisign cannot publish a delegation pointing to servers the new manager does not control β the technical check at step four fails. The change stalls, and the old servers keep answering.
The resolution path runs through the country's authorities and IANA's mediation procedures, not through Verisign. Verisign's role is to execute a verified instruction. This is the practical demonstration of the policy-operations split: the operator cannot fix a political problem, and the policy body cannot publish a zone file.
Escalation in a real dispute has historically taken years, and the IANA function's published procedures document the expected timelines. If a delegation is contested, the root data stays as it is until the dispute resolves β an intentional design choice to prevent operational seizure.
Cost, Time, and Scale: What the Root System Actually Takes to Run
The root system's scale is a useful check on any claim that it is fragile. A root zone file is a few megabytes compressed. It is regenerated several times a day, and anycast means a query to A-root can be answered by a site on the same continent as the resolver.
ICANN's published budget offers one cost figure worth naming. Its fiscal year 2024β2025 operating budget ran to roughly 150 million U.S. dollars, covering policy development, IANA operations, and compliance work across the organization. Verisign's cooperative agreement does not involve a fee paid by ICANN to Verisign for root zone publication; instead, Verisign's economics come from the .com and .net registry businesses, and its root zone duties are tied to the same corporate relationship. That arrangement has been criticized on conflict-of-interest grounds for years β a company that profits from .com also operates the root zone that contains it. The counterargument is that the contract, the NTIA oversight, and ICANN's authorization requirement are the safeguards.
Put the numbers together and one conclusion follows: the root zone is small in bytes, cheap relative to the value it secures, and slow to change by design. The serial number is the single best audit signal of what changed and when.
FAQ
Does Verisign own the root zone file?
No. Verisign operates the authoritative root zone publication service under a cooperative agreement with NTIA and executes changes authorized through ICANN's IANA function. The zone is treated as a public trust, and the contract structure exists so no single party, including Verisign, can alter delegations unilaterally. If the arrangement ended, the operational duty would be reassigned.
If ICANN and Verisign are the two organizations, why does NTIA still appear in documents?
NTIA, an agency of the U.S. Department of Commerce, is a party to the cooperative agreement that governs Verisign's root zone maintenance duties and must approve major changes to those arrangements. Separately, NTIA's IANA stewardship contract with ICANN expired in 2016. The two relationships are distinct, and NTIA's residual oversight applies to Verisign, not to ICANN's policy decisions.
Can a single root server operator refuse to publish an ICANN-approved change?
In principle an operator runs its own infrastructure, but in practice the zone file comes from the publication service, and operators refresh from it. A refusal would mean serving stale data, which resolvers would eventually detect through serial number comparison. The system relies on cooperation backed by technical checks, not on direct command authority β which is why the Root Server System Advisory Committee exists.
How many physical servers actually serve root DNS queries?
Far more than thirteen. The thirteen named identities are anycast addresses, and behind them sit hundreds of physical server instances distributed across data centers worldwide. Anycast routing sends a query to the nearest site announcing the address. This design lets two operators β Verisign and ICANN β each run one or two identities while global coverage is achieved across the whole set.
What happens to my domain if the root zone has a publication error?
The domain itself stays in its registry; the problem is that resolvers may not find the top-level domain's name servers. Most resolvers cache root data briefly and refresh from a working source, so a single malformed publication is usually corrected on the next generation cycle. Verisign publishes the zone's serial number and change log, which is the fastest way to confirm whether a change has propagated.
Is the ".com registry" the same thing as the "root zone"?
No. The .com registry, run by Verisign, holds the records for every second-level name under .com. The root zone holds only the delegation for .com as a whole β its name servers. A change to a .com domain updates the .com zone, not the root. Confusing the two is one of the most common errors in explanations of the system.
Could one company take over both root publication and .com registry duties without conflict?
That is the present arrangement, and the conflict has been debated for over two decades. The safeguards are the cooperative agreement's conditions, the requirement that ICANN authorize changes, and public reporting. Whether those suffice is a policy judgment, not a technical fact, and the debate continues in ICANN's public comment processes.
The system described here rests on contracts, procedures, and cooperative relationships rather than on any single authority's command. It is a stable design precisely because each layer checks the next, and because the organizations involved publish enough documentation that an outsider can trace any change from request to live answer.