What is IP address allocation?
IP address allocation is the controlled distribution of an IP address or prefix for use within a defined scope. On the public Internet, IANA, Regional Internet Registries (RIRs), providers, and organizations distribute globally unique number resources through a policy and registration hierarchy. Inside a local network, an administrator, router, DHCP server, or IPv6 mechanism configures addresses on interfaces.
Those are related but different processes. A public prefix registration does not configure a laptop, and a DHCP lease on Wi-Fi does not grant a commercial right to use public IPv4 space. In both cases, the useful record includes the address or CIDR, who controls it, where it applies, how long it applies, and what routing or configuration is still required.
What does “IP allocation” mean?
| Layer | What is distributed | Typical authority | What it does not prove |
|---|---|---|---|
| Internet number resources | A globally unique IPv4 or IPv6 prefix | IANA, an RIR, an ISP or other authorized provider, and the registered organization | That the prefix is routed, application-ready, transferable, or commercially available |
| Local network configuration | An address and related settings for an interface | A network administrator, DHCP server, router, SLAAC, DHCPv6, or manual configuration | Ownership of the public egress address or permission to announce a public prefix |
Registry terminology can also distinguish an allocation made for further distribution from an assignment intended for an organization or end site. Exact definitions and eligibility come from the applicable RIR policy and resource status, so read the authoritative record rather than inferring rights from the word alone.
How are public IP addresses allocated?
- IANA coordinates the global pools. IANA provides pools of unallocated IP addresses and AS numbers to the five RIRs under global policy. It normally does not allocate an address directly to a home user or ordinary business endpoint.
- RIRs administer resources by service region. AFRINIC, APNIC, ARIN, LACNIC, and the RIPE NCC distribute and register resources under their community-developed policies.
- Providers and organizations manage the next layer. An ISP may assign addresses from its allocation to customers. A qualifying organization may hold provider-independent resources or receive a direct assignment, depending on current policy.
- The operator configures the network. The organization still needs an addressing plan, routes, DNS, security controls, monitoring, and lifecycle records before an address is useful.
IANA reports that its general IPv4 supply is exhausted. RIRs may still distribute limited recovered or policy-reserved IPv4 space, and registered IPv4 resources can move through approved transfer processes. IPv6 allocation continues. “Exhausted” therefore means the former unrestricted allocation model cannot meet normal demand; it does not mean every IPv4 address is routed, unavailable, or for sale.
Use the RIR guide to identify the responsible registry and the separate IPv4 address guide for address and prefix fundamentals.
Public and private IP allocation are different
A public address must be globally unique within the public routing system. Registration is necessary evidence about the resource, but Internet reachability also depends on an authorized route, upstream acceptance, security policy, and a working service.
RFC 1918 reserves 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 for private IPv4 networks. Different organizations can reuse those ranges because they are not globally unique or routed across the public Internet. A router may use NAT or another gateway function so private endpoints can reach external services through a public address.
An address such as 192.168.1.20 can be properly allocated inside one home or office and still have no meaning on another network. See the public versus private IP guide for scope, NAT, and reachability details.
How do DHCP, static, and dynamic allocation work?
| Method | How the address is selected | Best use | Record to keep |
|---|---|---|---|
| Dynamic DHCP | A DHCP server offers an available address from a defined pool for a lease period | Client devices and workloads that may join, leave, or move | Pool, lease time, client identifier, timestamps, gateway, DNS, and server logs |
| DHCP reservation | The server maps a known client identifier to a predictable address | Managed devices that need stable local addressing without manual host configuration | Reservation owner, identifier, address, exclusions, and change history |
| Manual or static | An administrator configures the address on the interface | Infrastructure where the operating design requires a fixed address | Prefix, gateway, DNS, owner, duplicate check, purpose, and rollback |
| IPv6 SLAAC or DHCPv6 | Router Advertisements, interface behavior, and optionally DHCPv6 provide IPv6 addressing or configuration | IPv6 networks designed for the selected host and prefix-delegation model | Prefix, router policy, address-generation method, DHCPv6 state, DNS, and lifetime |
DHCP for IPv4 commonly follows Discover, Offer, Request, and Acknowledge exchanges. The resulting DHCP lease is a temporary local configuration record. It is unrelated to an agreement to lease a public IPv4 block from a resource holder.
Static does not mean permanent ownership, and dynamic does not mean random or uncontrolled. Both need a valid subnet, a unique address within that scope, a gateway and DNS plan where required, and a source of truth such as IP address management (IPAM).
What is IP allocation in Wi-Fi?
When a device joins Wi-Fi, the access point provides the wireless link and the connected network usually supplies IP configuration. In a typical home network, the router's DHCP server offers the device a private IPv4 address, subnet information, a default gateway, DNS servers, and a lease time. The router then uses a separate public address for Internet access, often with NAT.
The allocated Wi-Fi address can change after a lease expires, the device joins another network, the DHCP pool changes, or the client presents a different identifier. A device can also have IPv4 and several IPv6 addresses at the same time. Seeing “allocated address” in a Wi-Fi status screen therefore describes current interface configuration, not who owns the public Internet resource or who is using the device.
How should a network plan IP address allocation?
- Define the scope. Record the parent prefix, sites, VLANs or routing domains, address family, trust boundaries, and whether the space is public, private, shared, or special-purpose.
- Size prefixes from interfaces and growth. Include gateways, redundancy, infrastructure, temporary capacity, and platform constraints. Do not choose a familiar subnet size without the requirement.
- Separate pools and exclusions. Keep infrastructure, client, guest, VPN, container, and management needs explicit. Prevent DHCP from offering manually configured addresses.
- Record every dependency. Maintain prefix, owner, purpose, status, gateway, DHCP, DNS, route, firewall, NAT, monitoring, and retirement data in IPAM or another authoritative system.
- Validate before activation. Check overlap, duplicate use, first and last address, return routes, DNS, policy, failover, logging, and rollback with approved test traffic.
- Reclaim deliberately. Expire or remove old leases, reservations, DNS, routes, allowlists, cloud bindings, and documentation only after confirming that the address is no longer referenced.
The subnetting guide explains how to divide a parent prefix without overlap and why an address boundary is not automatically a security boundary.
How can an organization obtain public IPv4 space?
| Path | What the organization receives | What still needs verification |
|---|---|---|
| ISP or hosting assignment | Use of provider address space with a connectivity or hosting service | Portability, routing control, term, reverse DNS, and return conditions |
| Direct RIR resource | A registration under the applicable RIR's current policy | Eligibility, ongoing obligations, routing, DNS, security, and application fit |
| Approved transfer or purchase | Longer-term control after the applicable registry transfer completes | Counterparty authority, transfer approval, payment, condition, routing, and integration |
| IPv4 lease | A time-limited contractual right to use an exact prefix | Lessor authority, origin authorization, RPKI and IRR work, price, support, renewal, and return |
For a leased or transferred prefix, preserve the exact CIDR, authoritative registry record, contract, origin ASN, LOA where required, IRR objects, RPKI ROA, reverse DNS, reputation observations, abuse path, activation evidence, renewal, and exit plan. Allocation alone does not prove that a prefix is safe or ready to serve traffic.
IP address allocation FAQ
What is IP allocation in simple terms?
It is the controlled distribution of an IP address or prefix for use within a defined scope. The term can refer to public Internet number resources or to address configuration inside a local network.
What is an allocated IP address?
It is an address currently set aside or configured for a stated interface, customer, service, or network purpose. The record should identify the scope, authority, duration, and related prefix; the word “allocated” alone does not prove ownership or reachability.
Who controls the allocation of public IP addresses?
IANA coordinates global pools and provides resources to the five RIRs. RIRs, ISPs, and other authorized providers then distribute or assign resources under applicable policy and agreements. The receiving network remains responsible for configuration and operation.
What is IP allocation in Wi-Fi?
It usually means the local network has configured an address on the device, commonly through DHCP for IPv4 and SLAAC or DHCPv6 for IPv6. The address may be private and different from the router's public egress address.
What is the difference between static and dynamic IP allocation?
A static address is configured or reserved to remain predictable; a dynamic address is selected from a pool for a lease period. Either method can fail without correct prefix, gateway, DNS, duplicate prevention, and lifecycle records.
Is a DHCP lease the same as leasing public IPv4 space?
No. A DHCP lease is a local configuration with a lifetime. A public IPv4 lease is a commercial agreement granting time-limited use of a prefix and requires separate authority, routing, registry, and operating checks.
Does receiving a public IP allocation make it reachable?
No. Public reachability also requires a route accepted by the relevant networks, working next hops, security policy, DNS where needed, and a service configured to receive traffic.
Can private IP addresses be reused?
Yes. RFC 1918 private IPv4 ranges can be reused by separate networks because they are not globally unique. Overlap can still create problems when those networks later connect through a VPN, merger, cloud link, or other routed path.
Primary sources
- IANA: Number Resource Allocation Data
- RFC 1918: Address Allocation for Private Internets
- RFC 2131: Dynamic Host Configuration Protocol
- RFC 4291: IPv6 Addressing Architecture
- RFC 4862: IPv6 Stateless Address Autoconfiguration
- RFC 8415: DHCP for IPv6
Use allocation facts to choose the next address path
Separate registry authority, local configuration, routing, and commercial rights before treating any address as available. If the requirement is public IPv4 capacity, compare the complete operating path rather than the allocation label alone.
Review the IPv4 leasing workflow or open the IPv4 operating knowledge base.
