IPAM — IP Address Management
IPAM is your source of truth for address space. It models your networks as a hierarchy of containers and networks, tracks individual IP addresses, and cross-links to DNS and DHCP so your records and reservations stay aligned with your plan.
Open it from Network Operations → IPAM → Subnets. The header shows totals (containers, networks, tracked addresses) and overall utilization.
In this section
- Subnets — create containers and networks, organize the hierarchy, assign sites, and allocate space.
- IP addresses — inspect a network's addresses and jump to DNS/DHCP from any IP.
- Split & merge — divide a network into children or combine adjacent siblings.
- Inherited options — set DNS/DHCP defaults on a container that flow down to its networks.
Containers vs. networks
| Container | Network (leaf) | |
|---|---|---|
| Purpose | Organize address space | Track individual IPs |
| Example | 10.0.0.0/8 | 10.10.1.0/24 |
| Holds | Other containers/networks | IP addresses |
| Tracks utilization | No (organizational) | Yes |
| Can set inherited options | Yes | Yes (its own) |
How IPAM connects to the rest of Subnetly
- Creating a network can automatically create its matching reverse DNS zone.
- From any IP address you can add an A record (DNS) or a reservation (DHCP) — the editor opens pre-filled.
- Subnets can be assigned to sites, and containers cascade the assignment to children.
- Containers can carry DNS/DHCP options that child networks inherit.
Quick tasks
| I want to… | Go to |
|---|---|
| Add a new network or container | Create a subnet |
| Carve a block out of a container | Allocate / split |
| Track or label an IP, add DNS/DHCP from it | IP addresses |
| Set defaults that flow to child networks | Inherited options |
| Bulk-load subnets from CSV | Import tools |