The Internet Assigned Numbers Authority, commonly known as IANA, coordinates several globally unique identifiers that allow the Internet’s networks, applications and services to operate together.

IANA has three principal areas of responsibility:

· Coordinating the Domain Name System root zone

· Managing the global pools and registries for IP addresses and Autonomous System Numbers

· Maintaining registries for Internet protocol parameters

The IANA functions are among the Internet’s oldest technical coordination activities. Today, these functions are performed by Public Technical Identifiers, or PTI, an affiliate of the Internet Corporation for Assigned Names and Numbers, commonly known as ICANN.

Most people and businesses never communicate with IANA directly. However, its work supports many everyday Internet activities, including opening a website, sending an email, operating cloud infrastructure and routing traffic between networks.

IANA does not operate the entire Internet or allocate ordinary IP addresses directly to every business. Its principal role is technical coordination: maintaining authoritative records so that important Internet names, numbers and protocol values remain unique and consistently understood.

What Does IANA Stand For?

IANA stands for Internet Assigned Numbers Authority.

It is useful to think of IANA as a central record keeper for several categories of globally significant Internet identifiers.

The Internet is decentralised and consists of thousands of independently operated networks. However, those networks still need to agree on the meaning and use of certain technical values.

For example:

· Two networks should not receive conflicting global IP address allocations.

· Each Autonomous System Number should identify a specific autonomous system.

· A protocol value should have the same meaning across different software and equipment.

· The DNS root should provide a consistent record of top-level domain delegations.

IANA maintains authoritative registries that help prevent these identifiers from being assigned inconsistently.

Why Does the Internet Need IANA?

No single company, government or organisation operates the entire Internet.

Internet service providers, cloud companies, hosting providers, governments, universities, enterprises and other organisations operate their own networks. Those independent systems can communicate because they use shared technical standards and coordinated identifiers.

Some identifiers must be globally unique.

If two unrelated organisations attempted to use the same publicly routed IP address block, routing conflicts could occur. If software developers assigned different meanings to the same protocol number, their systems might not communicate correctly.

IANA supports global interoperability by maintaining authoritative registries and implementing policies developed through the relevant technical and Internet governance communities.

Its role is therefore best understood as coordination rather than control.

What Are the Main Functions of IANA?

The work of the Internet Assigned Numbers Authority is divided into three main categories:

1. Domain names and DNS root-zone management

2. Internet number resources

3. Internet protocol parameters

1. DNS Root-Zone Management

The Domain Name System, or DNS, translates human-readable domain names into information that computers can use to locate Internet services.

The DNS follows a hierarchy. At the top of this hierarchy is the DNS root zone, which contains delegation information for top-level domains such as:

· .com

· .net

· .org

· .uk

· .de

· .my

IANA coordinates changes to the DNS root-zone database and maintains authoritative information about top-level domain delegations.

The root-zone database identifies the organisations responsible for top-level domains and records technical details such as their authoritative name servers.

IANA’s domain-related responsibilities also include:

· Managing information associated with the DNS root

· Administering the .int and .arpa domains

· Maintaining top-level domain delegation records

· Supporting internationalised domain-name practices

· Processing authorised root-zone change requests

· Maintaining relevant DNSSEC information

The official IANA Root Zone Database provides the delegation details for generic and country-code top-level domains.

Does IANA sell domain names?

No.

IANA does not normally sell or register individual domain names such as example.com.

Individual domain names are obtained through domain registrars. The general structure works as follows:

IANA root-zone coordination → top-level domain registry → domain registrar → domain registrant

For example, IANA maintains root-zone delegation information for .com. The .com registry maintains the authoritative database of registered .com domains, while registrars provide registration services to individuals and businesses.

Does IANA operate every DNS server?

No.

IANA coordinates authoritative root-zone information, but it does not operate every DNS server or every root-server instance.

Root-server infrastructure is operated by separate organisations through distributed global systems. Top-level domain registries manage their respective zones, while DNS providers and network operators run many other parts of the DNS infrastructure.

IANA’s responsibility is focused on coordination and maintenance of root-zone data rather than operation of the entire DNS.

2. IP Addresses and Autonomous System Numbers

IANA coordinates the global pools and registries for Internet number resources.

These resources primarily include:

· IPv4 addresses

· IPv6 addresses

· Autonomous System Numbers, or ASNs

IANA maintains the top-level number-resource registries and provides large blocks of unallocated addresses and AS numbers to the five Regional Internet Registries.

The five RIRs are:

egional Internet Registries then allocate or assign resources within their respective service regions according to applicable policies.

A simplified version of the number-resource hierarchy is:

IANA → Regional Internet Registry → Local or National Internet Registry → ISP or network operator → customer

The precise path may vary. Some organisations receive resources directly from an RIR, while others obtain them through an Internet service provider, Local Internet Registry, cloud provider, hosting company or specialised IP address provider.

Read LARUS’s guide to regional Internet registries for a more detailed explanation of the five RIRs and their functions.

IANA and IPv4 addresses

IPv4 addresses are 32-bit numerical identifiers. They are commonly written in dotted-decimal format, such as:

192.0.2.1

IANA maintains the global IPv4 address-space registry, which records how large sections of the address space have been allocated, reserved or designated for specific purposes.

IANA does not ordinarily issue IPv4 address blocks directly to individual businesses or Internet users.

Because the central pool of previously unallocated IPv4 addresses has been exhausted, organisations seeking additional IPv4 resources generally obtain them through:

· Regional transfer processes

· IPv4 leasing arrangements

· Internet service providers

· Hosting or cloud providers

· Organisations with existing IPv4 resources

Understanding the source and registration history of an IPv4 block is important because address resources may pass through several organisations before reaching an end user.

IANA and IPv6 addresses

IPv6 was developed to provide a much larger address space than IPv4.

An IPv6 address uses 128 bits and may appear in a format such as:

2001:db8::1

IANA coordinates the global IPv6 address space and allocates large IPv6 blocks to Regional Internet Registries. The RIRs then distribute IPv6 resources within their service regions.

IPv6 adoption continues to expand, but IPv4 remains widely used because many existing networks, users and applications still depend on it.

For this reason, many organisations operate both protocols in a dual-stack environment.

IANA and Autonomous System Numbers

An Autonomous System Number identifies a network that operates an independent routing policy.

ASNs are used by the Border Gateway Protocol, or BGP, to exchange routing information between autonomous systems.

Internet service providers, cloud platforms, content delivery networks and large enterprises may require an ASN when they:

· Connect to multiple upstream providers

· Operate their own routing policy

· Announce their own IP address space

· Exchange routes with other networks

· Participate in an Internet exchange

IANA coordinates the global ASN pool and allocates ASN blocks to Regional Internet Registries. The RIRs then assign individual ASNs to eligible network operators.

IANA does not assign AS numbers to different routing protocols. Instead, it coordinates the number space used to identify autonomous systems participating in interdomain routing.

3. Internet Protocol Parameters

Internet communication depends on more than IP addresses and domain names.

Internet protocols also use standardised numbers, codes, names and other technical values. IANA maintains authoritative registries for many of these protocol parameters in coordination with Internet standards organisations.

Examples include registries covering:

· Port numbers

· Internet protocol numbers

· Media types

· DNS parameters

· HTTP fields

· TLS parameters

· Address families

· Uniform Resource Identifier schemes

· Routing-protocol values

· Internet message formats

· Language-related identifiers

· Time-zone information

These registries help ensure that different developers, applications and network devices interpret assigned values consistently.

Protocol and port-number examples

Applications and transport protocols use port numbers to identify particular services or communication endpoints.

A central registry allows developers and network operators to determine whether a port number has been assigned and which service or protocol is associated with it.

IP headers also contain fields identifying the protocol carried within a packet. Coordinated assignments help prevent unrelated technologies from assigning conflicting meanings to the same value.

Does IANA create Internet standards?

No.

Internet standards are generally developed by technical communities and standards organisations, particularly the Internet Engineering Task Force, or IETF.

A technical standard may include instructions explaining whether IANA should:

· Create a new registry

· Add a value to an existing registry

· Reserve a range of values

· Apply a particular registration policy

· Update an existing assignment

IANA then performs the required registry action according to the approved procedure.

The technical community develops the standard. IANA maintains the resulting authoritative record.

Does IANA Set Internet Policy?

IANA does not independently create most of the policies it implements.

Different communities develop policies for different IANA functions:

· ICANN’s multistakeholder structures develop policies affecting domain names.

· The Regional Internet Registry system develops global and regional number-resource policies.

· The IETF develops technical standards and protocol-parameter procedures.

IANA’s role is primarily operational. It processes authorised requests and maintains registries according to established policies and technical standards.

This separation between policy development and implementation is important for accountability. The organisation maintaining a registry should not invent new rules for individual requests without an established process.

However, the governance processes surrounding IANA and ICANN remain subjects of debate. Lu Heng’s note The Multi-Stakeholder Mirage offers a critical perspective on the difference between participation in an Internet governance process and having an authorised mandate to make binding decisions for absent parties.

The multistakeholder model provides a way for governments, businesses, technical experts and civil-society groups to participate in Internet coordination. At the same time, participation, technical expertise and legal authority should not automatically be treated as the same thing.

What Is the Difference Between IANA and ICANN?

IANA and ICANN are closely connected, but they are not identical.

ICANN is the broader nonprofit organisation involved in coordinating systems of unique Internet identifiers and supporting related policy-development processes.

IANA refers to specific technical functions involving:

· Domain-name coordination

· Internet number-resource coordination

· Protocol-parameter registries

The IANA functions are performed by Public Technical Identifiers, an affiliate of ICANN.

A simplified explanation is:

· ICANN: The broader organisational and policy framework

· PTI: The legal entity that performs the IANA functions

· IANA: The technical coordination functions and services

In ordinary discussion, people often use “IANA” to refer collectively to the functions, services and operational team.

What Is the Difference Between IANA and an RIR?

IANA coordinates Internet number resources at the global level. Regional Internet Registries manage and register them at the regional level.

For example, an Internet service provider in Malaysia would not normally request ordinary IP address space directly from IANA. It would generally operate within the APNIC service region.

An organisation in Europe would typically work with RIPE NCC, a Local Internet Registry or another provider operating within the RIPE NCC system.

The regional structure was created as a practical way to scale number-resource administration. However, a service region should not automatically be confused with political representation or territorial ownership.

Who Gets to Speak for a Continent, a Community, or the End User? examines this distinction. The note argues that an organisation’s responsibility for administering resources in a region does not necessarily give it a political mandate to speak for every network, business, government or Internet user within that region.

What Is the Difference Between IANA and a Local Internet Registry?

A Local Internet Registry, or LIR, is normally an Internet service provider, telecommunications company, hosting provider or other organisation that receives Internet number resources for its own network or customers.

IANA operates at the global level, while an LIR operates much closer to the end user.

The approximate hierarchy is:

IANA → RIR → LIR → customer

An LIR may assign IP addresses to customers, maintain relevant registration information and assist with routing-related arrangements.

Does IANA Control the Internet?

No single organisation controls the entire Internet.

The Internet consists of independently operated networks that use compatible standards and coordination systems.

IANA has an important role because it maintains globally authoritative registries, but it does not:

· Own every IP address

· Operate every Internet router

· Control every DNS server

· Decide which BGP routes networks must accept

· Register every individual domain name

· Write every Internet standard

· Provide Internet access to end users

· Regulate all online content

IANA’s influence comes from trusted technical coordination rather than centralised command over the Internet.

IANA, Internet Governance and IP Address Sovereignty

IANA’s coordination role is sometimes confused with ownership or sovereign control over Internet number resources.

These are different concepts.

Maintaining an authoritative registry does not necessarily give an organisation conventional ownership of everything recorded within that registry. Similarly, allocating a large IP address block within the registry hierarchy does not mean IANA operates or owns the networks using those addresses.

The Internet crosses national borders and legal jurisdictions. Its physical infrastructure is owned and operated by many different organisations, while its technical identifiers are coordinated through global institutions and processes.

Internet Governance and IP Address Sovereignty: Myth or Reality? explores this distinction in greater detail. It argues that technical coordination should not be confused with territorial ownership or unrestricted sovereign power over digital identifiers.

This distinction matters to network operators because several different forms of authority may be involved in an IP address deployment:

· Registry authority

· Contractual rights

· Applicable national law

· Resource registration

· BGP routing control

· Upstream-provider relationships

· RPKI and routing-security arrangements

These areas may overlap, but they are not identical.

A registry may maintain the authoritative registration record for an IP address block. However, the actual routing of that block depends on BGP announcements, upstream providers, network policies and independent routing decisions.

Why Is IANA Important to Network Operators?

Network operators rely on globally consistent information about IP addresses, Autonomous System Numbers and protocol values.

IANA’s work helps ensure that:

· Global IP address allocations are documented.

· AS number ranges are distributed without conflicting assignments.

· RIRs can obtain number resources through established procedures.

· Reserved and special-purpose address ranges are identified.

· Protocol values have consistent meanings.

· DNS root-zone delegation information remains authoritative.

· Technical standards can reference stable registries.

A business may never communicate directly with IANA, but its IP addresses and ASN still form part of the global system that IANA coordinates.

Understanding that system helps network operators determine:

· Where their resources originated

· Which RIR administers their registration

· Which organisation controls the relevant registry account

· How routing information will be maintained

· Which policies apply to an allocation or transfer

· How a resource can be used across different regions

Why Accurate Internet Registries Matter

Internet communication depends on independent systems interpreting technical identifiers consistently.

If authoritative registries were inaccurate or conflicting:

· Different networks could claim the same number resource.

· Software could interpret the same protocol value differently.

· DNS resolvers could receive inconsistent root-zone information.

· Network troubleshooting could become more difficult.

· Infrastructure providers could struggle to verify resource status.

· Transfers and routing-security arrangements could become less reliable.

At its most basic level, Internet number-resource coordination exists to preserve uniqueness and maintain accurate records.

Lu Heng’s Bill of Rights of Uniqueness Coordination presents a deliberately narrow view of the registry mandate. It argues that a number registry should protect uniqueness, maintain accurate records and support operational continuity without converting its administrative function into unrestricted authority over networks or resources.

Accurate registries do not guarantee that every network will operate without disruption. They do, however, provide essential reference points for interoperability and global coordination.

Conclusion

The Internet Assigned Numbers Authority performs an essential technical coordination role within the global Internet.

Its three main responsibilities are:

1.       Coordinating DNS root-zone information

2.       Managing global IP address and Autonomous System Number registries

3.       Maintaining Internet protocol-parameter registries

IANA helps ensure that important Internet identifiers remain unique, authoritative and consistently understood.

However, IANA does not operate every network or directly control how all Internet resources are used. Its role sits within a broader ecosystem that includes ICANN, PTI, the IETF, Regional Internet Registries, Local Internet Registries, Internet service providers and independent network operators.

Understanding this hierarchy helps businesses determine where their IP resources originate, which organisation maintains their registration and how those resources become usable within real network infrastructure.

For organisations using IPv4 addresses, IPv6 addresses or ASNs, accurate registration is only one part of a reliable deployment. Routing control, contractual clarity, provider accountability and operational continuity also matter.

LARUS supports organisations that require IPv4 resources for hosting, cloud infrastructure, telecommunications and other network deployments. Contact the LARUS team to discuss your IP address requirements and identify an approach suited to your operational needs.