What is IP Address Management
Understand IPAM through an everyday address conflict: how planning, DHCP, DNS and live observations fit together, and why records need context.
Two teams are preparing new services. Each sees the same address marked “available” and assigns it. Individually, both changes look reasonable. Together, they can leave traffic reaching the wrong destination or failing altogether.
IP address management, usually shortened to IPAM, is the practice of planning address space and keeping a usable record of assignments. It helps people answer four questions: what space do we have, what is it for, who is using it and what can we safely change?
What belongs in the record?
An address identifies an interface or service within a network context. A prefix describes a block of addresses. The IPAM record connects those numbers to their purpose: an office, a customer network, a cloud environment or a particular service.
It should distinguish available, reserved, assigned and retiring resources. Each entry needs a responsible team, its routing context, the source of the information and when it was checked. A future project can have a valid reservation even when no device is using the address today.
IPAM, DHCP and DNS do different jobs
Imagine opening a new office. The address plan sets aside a block for that site. A DHCP service can give a laptop an address and other network settings for a lease period. DNS lets people and software find services through names. IPAM records how that space is organised and relates assignments to the wider plan.
Products that integrate all three are often called DDI platforms. Integration can keep changes aligned, but an IPAM entry alone does not configure a router, authenticate a user or make an application reachable. Those effects depend on the connected systems and their actual configuration.
A plan and a live network can disagree
Discovery tools, DHCP leases, device records and cloud APIs provide observations. Compare them with intended assignments. An unexpected device needs investigation; an apparently absent one may be sleeping, behind a filter or reserved for recovery.
Suppose a server has been removed but its address remains in a partner's access list. Reassigning it can have consequences even though the old server never responds to a scan. Retirement therefore includes checking dependencies and confirming the service is finished before the address becomes available again.
Repeated numbers need context
Two offices can use the same private range independently. Trouble may appear when they are connected through a VPN or a company merger. Separate routing domains can also deliberately contain overlapping space. A VRF represents an independent routing table, helping keep those contexts distinct.
The important record is therefore more than the number alone. It includes where that number applies and which networks are expected to communicate. This makes a future connection easier to plan before it becomes a live routing problem.
IPv4 and IPv6 need explicit plans
IPv4 and IPv6 are different address families. Dual-stack operation supports both; it does not mean every device has exactly two addresses. An interface may have several IPv6 addresses, including addresses formed through stateless autoconfiguration. Temporary addresses also make a simple device-to-address list incomplete over time.
Manage prefixes, lifetimes and sources of observation as well as individual addresses. An IPAM product only sees what its integrations can observe. Protocol choices should follow service reachability, equipment support and operational needs. The size of IPv6 space does not remove the need for planning, and better IPv4 management remains useful wherever IPv4 services operate.
Give teams a shared view without a single bottleneck
A shared inventory can support delegated management: each site handles its own allocations within agreed ranges while others can see the result. Keep durable identifiers, readable exports and change history. Decide how existing services and urgent provisioning will behave if the management tool becomes unavailable.
Begin with one environment. Reconcile its records, identify the people responsible and test one complete assignment and retirement. Measure whether colleagues can answer the four opening questions more easily. Expand from that evidence.
There is a wider distinction behind this everyday engineering work. Lu Heng argues in Note 67 that providing a coordination service does not make the provider sovereign over its users. Inside a network, too, the record exists to help people operate. Continue with how to evaluate IPAM tools.