IP Address Management (IPAM) for Hosting: Subnets, VLANs, and Auto-Allocation

Every hosting provider eventually hits the same wall. You start with a /24 subnet and a spreadsheet. Columns track which IPs are assigned, to whom, and for what service. It works fine with 50 IPs. At 500, the spreadsheet has merge conflicts, outdated entries, and that one row where nobody remembers who 203.0.113.47 belongs to.

IP Address Management (IPAM) software solves this by turning manual tracking into a structured, automated system. FluxBilling includes a full IPAM suite built directly into the billing and provisioning platform — no separate tools, no integration headaches.

The Problem with Manual IP Management

Manual IP tracking fails in predictable ways:

• Stale records — An IP is freed when a service is cancelled, but nobody updates the spreadsheet. The next allocation skips it, wasting addresses.
• Duplicate assignments — Two engineers allocate the same IP to different services because they were both looking at an outdated copy.
• No audit trail — When a client reports their IP was reassigned, you have no history of who changed it and when.
• Subnet exhaustion surprises — You run out of IPs in a subnet because there is no real-time visibility into utilization.
• VLAN chaos — VLANs are configured on switches but not tracked in any central system, leading to misconfigurations.

Once you cross 100 managed IPs, these problems become daily operational friction.

FluxBilling IPAM: Core Features

Subnet Management

FluxBilling tracks subnets hierarchically. You start with your allocated blocks and subdivide them:

• Supernet — Your large allocation from ARIN or RIPE (e.g., 203.0.113.0/22)
  • Subnet — A subdivision for a specific datacenter (e.g., 203.0.113.0/24)
    • Sub-subnet — A further split for a rack or VLAN (e.g., 203.0.113.0/26)

Each subnet tracks:

• CIDR notation with full validation for both IPv4 and IPv6
• Allocation status — Unallocated, allocated to a device, or allocated to a VLAN
• Description — Human-readable label for quick identification
• Auto-allocatable flag — Mark subnets that should be used for automatic provisioning allocation
• Location association — Link subnets to specific datacenters or locations

The hierarchical view lets you see your entire IP estate at a glance. Drill into any supernet to see its subdivisions, utilization, and available space.

IPv6 Support

IPv6 is a first-class citizen in FluxBilling''s IPAM, not an afterthought:

• Full IPv6 CIDR notation support (/48, /64, /128, etc.)
• IPv6 address compression and expansion
• BigInt-based calculations for the large address space
• Subnet splitting and merging for IPv6 blocks
• Mixed IPv4/IPv6 display in the same interface

VLAN Management

VLANs connect your logical network to your physical infrastructure:

• Create and configure VLANs with ID, name, and description
• Associate VLANs with subnets — Link one or more subnets to each VLAN
• Assign VLANs to devices — Track which VLAN each server or network port belongs to
• VLAN hierarchy — Organize VLANs by location, purpose, or tenant
• Auto-association — When allocating a subnet to a VLAN, child subnets can auto-associate

IP Address Allocation

Allocation is where IPAM saves the most time:

• Manual allocation — Assign specific IPs to devices with a click
• Automatic allocation — The system picks the next available IP from a designated subnet
• Allocation to devices — Physical servers, blade servers, and network devices all supported
• Allocation to services — When a client orders a server, IPs are allocated automatically during provisioning
• Allocation history — Full audit trail showing who allocated which IP, when, and to what

The automatic allocation respects rules you configure:

• Skip gateway and broadcast addresses automatically
• Respect subnet boundaries and VLAN associations
• Prevent allocation from subnets with child subnets (to avoid fragmenting your hierarchy)
• Allocate sequentially or from available pools based on preference

Auto-Allocation on Service Provisioning

This is the feature that ties IPAM directly into your revenue operations. When a client orders a dedicated server:

1. FluxBilling matches the order to available hardware (via the allocation engine)
2. IPAM allocates a primary IPv4 from the configured subnet for that product
3. If the client ordered additional IPs, those are allocated from the same or a specified subnet
4. IPv6 block is allocated if configured
5. VLANs are associated automatically
6. All allocations are recorded in the history

The allocation rules are configured per product, so different products can draw IPs from different subnets. A European datacenter product pulls from European IP blocks, while a US product pulls from US blocks.

If a subnet is exhausted, the system flags it and notifies admins rather than silently failing. No more discovering you are out of IPs when a client''s server is halfway through provisioning.

Advanced IP Utilities

Under the hood, FluxBilling includes a comprehensive IP utility library:

• Subnet overlap detection — Prevents creating subnets that conflict with existing allocations
• Subnet splitting — Divide a /24 into two /25s or four /26s with automatic recalculation
• Subnet merging — Combine adjacent subnets back into a larger block
• Available IP range calculation — See exactly which IPs are free within any subnet
• IP-in-subnet validation — Verify that an IP address falls within a specific subnet

These utilities power both the admin interface and the automated allocation engine.

Integration with Rack Management

IPAM does not exist in isolation. In FluxBilling, it connects directly to rack management:

• Allocate IPs to specific devices in specific rack positions
• View IP assignments alongside physical location in the rack diagram
• Track which IPs are associated with which network switch ports
• See subnet utilization broken down by datacenter and rack

This integration means you can answer questions like "which IPs are assigned to servers in Rack A3?" without cross-referencing multiple systems.

Standalone IPAM Tools vs. Integrated Approaches

Standalone IPAM tools such as NetBox are well-suited to network engineering teams who want a dedicated, specialized tool. Based on the NetBox documentation, it offers strong IPAM and network modeling features. For hosting providers who also want their IP allocation tied directly to billing and provisioning, an integrated approach can simplify the workflow:

• Your billing system knows about your IP allocations in the same database
• Your IPAM knows about your clients and services without syncing
• Provisioning does not require custom scripts to bridge systems
• Auditing happens against one database instead of correlating across several

FluxBilling''s integrated approach means one database, one admin panel, and one audit trail. When a client cancels a service, their IPs are automatically freed. When you need to know who has IP 203.0.113.47, the answer is one click away with the client name, service, and allocation date attached.

Read more about the full DCIM suite in our DCIM comparison or explore how IPAM powers automated provisioning.

Start your free trial to manage your IP estate from the same platform that handles your billing.

NetBox and any other third-party product names mentioned in this article are trademarks of their respective owners. FluxBilling is not affiliated with or endorsed by any of these companies. Feature information about third-party products is based on publicly available documentation as of February 2026 and may not reflect recent changes.