What Is IANA — and Why Does the Entire Internet Depend on It?

The Invisible Function Behind Every Domain Name, IP Address, and Internet Protocol — Explained Simply

Right now, billions of people are using the internet — sending emails, loading websites, streaming video, running businesses. Every single one of those connections depends on a system of numbers and names that just works. Domain names resolve. IP addresses route correctly. Protocols behave the same way everywhere.

Most people never wonder why this works. The answer, in large part, is a function called IANA — the Internet Assigned Numbers Authority.

IANA does not build websites, host servers, or run internet service providers. What it does is far more fundamental: it coordinates the global pool of numbers, names, and parameters that make internet communication possible. Without IANA — or something doing what IANA does — the internet as a universal, globally connected system could not exist.

This guide explains what IANA is, what it actually does, how it fits into the internet governance ecosystem alongside organizations like ICANN, APNIC, and ISOC, and why it matters to you even if you have never typed its name before today.

📌  One-Sentence Definition:  IANA — the Internet Assigned Numbers Authority — is the function responsible for coordinating three core resources that the entire internet depends on: the global Domain Name System (DNS) root zone, IP address allocation, and the registry of internet protocol parameters used by technical standards.

Where IANA Came From: A Brief History

IANA is one of the oldest ongoing functions on the internet — it predates the World Wide Web, predates most internet companies, and predates the public internet itself. Its origins go back to the 1970s and the earliest days of ARPANET, the US government-funded research network that eventually became the internet.

For the first two decades, IANA was essentially one person: Jon Postel, a computer scientist at the University of Southern California’s Information Sciences Institute. Postel had a remarkable ability to see that the internet would only work at scale if its fundamental resources — addresses, names, protocol identifiers — were coordinated by someone with a global view and the trust of the technical community. He did that job, informally but indispensably, from the 1970s until his death in 1998.

When Jon Postel died, the internet governance community faced a significant question: how do you institutionalize something that one person had done informally for thirty years? The answer was ICANN — the Internet Corporation for Assigned Names and Numbers — which was created in 1998 partly to provide an institutional home for the IANA functions. Since then, ICANN has performed the IANA functions under a framework that has evolved significantly, culminating in the 2016 IANA Stewardship Transition, which moved oversight from the US government to the global multi-stakeholder community.

🕰️  Historical Note:  The IANA function is often called a ‘function’ rather than an ‘organization’ because it describes what is done, not who does it. ICANN currently performs the IANA functions, but the function itself predates ICANN by decades and could in principle be performed by a different entity if the governance community decided that was appropriate.

What IANA Actually Does: The Three Core Functions

IANA’s work falls into three distinct areas, each essential to how the internet operates. Understanding all three is the key to understanding why IANA matters at every layer of the internet ecosystem.

1. Domain Name System (DNS) Root Zone Management

Every time you type a web address into a browser, the DNS translates that human-readable name into an IP address your computer can use to find the right server. The starting point for that translation process is the DNS root zone — a database that lists every Top-Level Domain (TLD) on the internet and the authoritative name servers responsible for each one.

IANA maintains this root zone database. Every .com, .org, .net, every country-code TLD like .uk, .ng, .jp, .de, and every new generic TLD like .shop, .tech, or .africa — all of them are listed in the DNS root zone that IANA coordinates. When a new TLD is created, when an existing TLD changes its name servers, or when a country-code TLD is redelegated to a new operator, that change goes through IANA’s processing and review before it appears in the root zone.

IANA also manages the DNSSEC Root Zone Key Signing Key — the master cryptographic key that anchors the security chain for the entire global DNS. Four times a year, IANA conducts publicly witnessed Root KSK Signing Ceremonies, bringing together Trusted Community Representatives from around the world to sign the Zone Signing Key in a process that is deliberately transparent, multi-party, and auditable.

• IANA processes all root zone change requests (new TLDs, name server updates, DNSSEC key changes)
• The root zone is published and served by root server operators — IANA coordinates the content, others distribute it
• Over 1,500 TLD entries are currently managed in the DNS root zone

2. IP Address Allocation

Every device on the internet needs an IP address — a unique numerical identifier that tells the network where to send data. IANA’s role in IP addressing is to allocate large blocks of IP address space to the five Regional Internet Registries (RIRs): APNIC (Asia Pacific), ARIN (North America), RIPE NCC (Europe, Middle East, and parts of Central Asia), LACNIC (Latin America and the Caribbean), and AFRINIC (Africa).

The RIRs then distribute these addresses to Internet Service Providers, national registries, and large organizations within their regions. IANA sits at the top of this allocation hierarchy — it does not assign individual IP addresses to individual devices or organizations; that happens at the RIR and ISP level. But without IANA’s oversight of the global address pool, the RIRs could not do their work in a coordinated way.

This applies to both IPv4 — the older, 32-bit address format now largely exhausted at the global level — and IPv6, the newer 128-bit format designed to provide enough addresses for billions of billions of connected devices. IANA coordinates the global allocation of both, and its records of which address blocks have been allocated to which RIR are the authoritative foundation for the entire global routing system.

• IANA allocates IP address blocks to the 5 RIRs — APNIC, ARIN, RIPE NCC, LACNIC, AFRINIC
• The IANA IPv4 free pool was fully exhausted in 2011 — all remaining IPv4 space is managed by the RIRs from their existing allocations
• IPv6 provides 340 undecillion addresses — IANA coordinates global IPv6 allocation to ensure no conflicts

3. Internet Protocol Parameters Registry

The third IANA function is the least well-known but arguably the most technically extensive: maintaining the registry of internet protocol parameters. Whenever the IETF (Internet Engineering Task Force) defines a new internet standard — a new protocol, a new extension to an existing protocol, a new identifier type — that standard typically requires some numbers or codes to be assigned so that different implementations can interoperate.

IANA is the registrar for those numbers. Port numbers, for instance — the identifiers that tell your computer whether incoming data is a web request (port 80 or 443), an email (port 25 or 587), or something else — are assigned and maintained by IANA. Protocol numbers, media type identifiers, character encoding identifiers, time zone database identifiers, and thousands of other technical parameters that are referenced in internet standards all live in IANA’s registries.

This registry work is what makes the internet’s technical standards usable across different systems and vendors. When a software developer writes code that sends a web request, they use port 443 for HTTPS — and they can count on that number meaning the same thing everywhere because IANA maintains the authoritative registry. Without this coordination, the protocols that make the internet work would be impossible to implement interoperably.

• IANA maintains over 3,000 individual registries covering internet protocol parameters
• Port numbers, protocol identifiers, MIME types, time zone data — all coordinated by IANA
• New registries are created when the IETF defines new standards requiring unique identifier assignment

IANA and ICANN: Understanding the Relationship

One of the most common points of confusion is how IANA and ICANN relate to each other. They are not the same thing, but they are closely linked.

ICANN — the Internet Corporation for Assigned Names and Numbers — is the nonprofit organization that currently performs the IANA functions. When you read about IANA making a root zone change, or IANA allocating IP address space to a Regional Internet Registry, the people actually doing that work are ICANN staff operating under the IANA functions mandate.

But IANA is not simply a department of ICANN. The IANA function is defined by its role, not by who performs it. Historically, it was performed by Jon Postel under a US government contract. After 1998, it was performed by ICANN under a contract with the US National Telecommunications and Information Administration (NTIA). In 2016, that US government oversight ended with the IANA Stewardship Transition — a landmark event in internet governance that transferred accountability from the US government to the global multi-stakeholder community, represented through ICANN’s own accountability structures and the Empowered Community.

The 2016 transition was significant because it established that no single government has authority over the IANA functions — a principle that reflects the internet governance community’s strong belief that the internet’s foundational infrastructure should be governed in the interests of all its users, not any single nation.

🔗  Quick Distinction:  IANA = the function (what gets done: DNS root zone, IP allocation, protocol parameters). ICANN = the organization currently performing that function. Think of it like a hospital (ICANN) that runs an emergency services department (IANA) — the department existed before the hospital had its current name, and the function is more fundamental than the institution performing it.

IANA’s Place in the Broader Internet Governance Ecosystem

IANA does not work in isolation. It sits at the center of a web of organizations and relationships that together constitute the internet’s technical coordination infrastructure.

IANA + ICANN: Policy and Operations ICANN develops the policies that govern how IANA performs its functions, particularly for the DNS. The GNSO (Generic Names Supporting Organization) and ccNSO (Country Code Names Supporting Organization) develop policies through community processes that IANA then implements operationally. When a new gTLD is approved, IANA handles the actual delegation into the root zone. When a ccTLD changes operators, IANA processes the redelegation following established criteria.

IANA + IETF: Standards and Parameters The IETF (Internet Engineering Task Force) creates the technical standards that define how internet protocols work. When a new standard requires unique identifiers, the IETF requests IANA to create and maintain the relevant registry. IANA’s protocol parameters registries are effectively the operational implementation layer for IETF standards — the bridge between a published RFC and actual interoperable network implementations.

IANA + RIRs: IP Address Hierarchy IANA works with APNIC, ARIN, RIPE NCC, LACNIC, and AFRINIC through a well-defined hierarchical system. IANA allocates large address blocks to the RIRs based on demonstrated need and established policy. The RIRs then distribute those blocks to ISPs and other organizations within their regions. Regular coordination between IANA and the RIRs ensures that the global IP address space is managed without conflicts or duplication.

IANA + Governments: The GAC and NTIA History Governments engage with IANA functions primarily through ICANN’s Governmental Advisory Committee (GAC) and, for ccTLD matters, through bilateral communication with the IANA function. Before 2016, the US NTIA had a formal oversight role. After the IANA Stewardship Transition, that government-specific oversight was replaced by community-based accountability mechanisms. IANA now operates under the community’s oversight rather than any single government’s authority.

IANA at a Glance: Key Facts

Fact	Detail
Full name	Internet Assigned Numbers Authority
Currently performed by	ICANN (Internet Corporation for Assigned Names and Numbers)
Founded / origins	1970s — Jon Postel at USC Information Sciences Institute
Institutionalized	1998 — ICANN created; IANA functions transferred under contract
IANA Stewardship Transition	October 2016 — oversight moved from US NTIA to global multi-stakeholder community
DNS root zone entries	1,500+ TLDs coordinated in the root zone database
RIRs served	5 — APNIC, ARIN, RIPE NCC, LACNIC, AFRINIC
Protocol registries	3,000+ individual registries covering internet protocol parameters
DNSSEC KSK ceremonies	4 times per year, publicly witnessed, live-streamed
Contact / info	iana.org — the official home of all IANA registries and documentation

Why IANA Matters — Even If You Never Think About It

IANA is one of those things that matters most when it works so well that nobody notices it. The consistency of the DNS root zone means that iginsight.org resolves the same way for a reader in Dhaka as it does for a reader in Oslo. The coordination of the IP address space means that data packets can travel across thousands of different networks and arrive at the right destination. The registry of protocol parameters means that an app built in India can communicate with a server in Brazil without either side needing to negotiate what port 443 means.

These are not trivial conveniences. They are the technical infrastructure of global communication — of economic activity, of education, of political organizing, of human connection across borders. IANA coordinates the underpinnings of all of it.

From an internet governance perspective, IANA is also significant because of what the 2016 stewardship transition demonstrated: that the internet’s most critical technical functions can be governed through a multi-stakeholder, community-accountable model rather than under any single government’s control. That outcome — which was contested, negotiated, and carefully designed over years — is one of the most important achievements in the history of internet governance. Understanding IANA means understanding why that achievement matters.

Frequently Asked Questions

Q1: Is IANA the same as ICANN?

No, though they are closely related. IANA is a function — a set of coordination responsibilities for the DNS root zone, IP addresses, and protocol parameters. ICANN is the organization that currently performs those functions. Before ICANN, IANA functions were performed by Jon Postel under a US government contract. The IANA function existed before ICANN did, and in principle could be performed by a different organization if the internet governance community decided that was appropriate. In practice, ICANN and IANA operate as closely linked entities, with ICANN providing the institutional home for IANA’s work.

Q2: Does IANA assign IP addresses to individual users or devices?

No. IANA allocates large blocks of IP address space to the five Regional Internet Registries (RIRs) — APNIC, ARIN, RIPE NCC, LACNIC, and AFRINIC. The RIRs then distribute smaller allocations to Internet Service Providers and organizations within their regions. Those organizations in turn assign individual IP addresses to their customers or devices. IANA sits at the top of this hierarchy, but ordinary internet users interact with IP addressing through their ISP, not directly with IANA.

Q3: What happened during the 2016 IANA Stewardship Transition?

From 1998 to 2016, ICANN performed the IANA functions under a contract with the US National Telecommunications and Information Administration (NTIA) — meaning the US government had formal oversight authority over IANA. The 2016 IANA Stewardship Transition ended that arrangement and replaced US government oversight with accountability to the global multi-stakeholder community through ICANN’s own Bylaws and the Empowered Community mechanism. This was a landmark moment because it established that no single government has authority over the internet’s foundational coordination functions.

Q4: What are the IANA protocol parameter registries?

When the IETF creates internet standards, those standards often require unique identifiers — port numbers, protocol codes, media type names, character encoding identifiers, and thousands of other technical parameters. IANA maintains the authoritative registries for these identifiers, ensuring that they mean the same thing everywhere on the internet. Without these registries, software developers and network engineers would have no reliable way to know which numbers and identifiers to use, making interoperability across different systems and vendors impossible.

Q5: Who oversees IANA today?

Since the 2016 Stewardship Transition, IANA’s oversight is distributed across the internet governance community. For the DNS root zone and domain name functions, ICANN’s GNSO and ccNSO communities provide policy oversight. For IP addressing, the five RIRs and the broader technical community provide oversight through the Number Resource Organization (NRO). For protocol parameters, the IETF provides oversight. ICANN’s Empowered Community — composed of the Supporting Organizations and Advisory Committees — has structural powers to hold ICANN accountable for how it performs the IANA functions.

Q6: How does IANA relate to APNIC, ARIN, RIPE NCC, LACNIC, and AFRINIC?

IANA allocates large blocks of IP address space to each of the five Regional Internet Registries (RIRs) at the top of the global IP address allocation hierarchy. The RIRs then distribute smaller blocks to ISPs and organizations within their respective regions. IANA’s records of these top-level allocations are the authoritative foundation for the entire global routing system. The five RIRs work cooperatively with IANA through the Number Resource Organization (NRO) to ensure global address space is managed without duplication or conflict.

Q7: What is the IANA DNS root zone, and why is it important?

The DNS root zone is a database that lists every Top-Level Domain (TLD) on the internet and the authoritative name servers responsible for each TLD. It is the starting point for all DNS resolution — when your computer looks up any domain name, the process ultimately traces back to the root zone to find which name server is authoritative for the relevant TLD. IANA maintains the content of this database. It has more than 1,500 TLD entries, and every change to it — adding a new TLD, updating name servers, modifying DNSSEC keys — goes through IANA’s processing and review before taking effect globally.

Q8: How can I get involved in internet governance processes related to IANA?

There are several ways to engage with IANA-related governance. For DNS and domain name policy, the ICANN GNSO (Generic Names Supporting Organization) develops policies that govern how IANA performs its DNS root zone functions — anyone can join GNSO working groups or submit public comments at icann.org/public-comments. For IP address policy, each RIR has an open policy development process where community members can propose and debate address policy. For protocol parameters, engagement happens through the IETF’s open standards process at ietf.org. IG Insight is a great starting point for understanding all of these pathways.

The Internet’s Foundations Are Governed by People. You Can Be One of Them. IANA is not a black box or a bureaucratic mystery — it is a set of coordination functions performed by real people through transparent, community-accountable processes. Understanding what IANA is and what it does is the first step toward understanding how the internet is governed, and why that governance matters for everyone who uses it. Explore more — and get involved: Keep Learning at IG Insight Visit iana.org — explore the live root zone database and protocol registries Read more on IG Insight: What Is ICANN? | What Is the IGF? | What Are RIRs? Take a free ICANN Learn course at learn.icann.org — Introduction to Internet Governance Join an ICANN Public Meeting (free virtually) at icann.org/meetings Participate in RIR policy processes — your region’s RIR has open community meetings Follow IG Insight at iginsight.org for plain-language internet governance updates   The internet was built by people who showed up, learned, and contributed. IANA, ICANN, the IGF, the RIRs — these are not closed clubs. They are open communities. IG Insight is your entry point.