Address Plan Generator

The Address Plan Generator creates structured IP address planning templates that serve as the foundation for professional network documentation and IPAM (IP Address Management) systems. Enter your parent network blocks (e.g., 10.0.0.0/8 or 172.16.0.0/12), define your organizational hierarchy, and get a complete spreadsheet template with columns for network address, CIDR, VLAN ID, gateway, DHCP scope, DNS servers, owner, and custom fields -- ready for CSV or JSON export.

Understanding IP Address Planning

An IP address plan is the blueprint that determines how every subnet, VLAN, and device fits together across your entire network. Without one, addressing decisions get made ad hoc -- one engineer picks 10.1.1.0/24 for the server room, another grabs 10.50.0.0/16 for a branch office, and six months later nobody can tell whether 10.1.2.0/24 is available or already in use somewhere. The routing table fills with disconnected entries that cannot be summarized, firewall rules reference subnets that have drifted from their original purpose, and adding a new site becomes a scavenger hunt through router configs.

A structured address plan prevents all of this by assigning meaning to address space hierarchically. A /16 per site, /24 blocks for individual VLANs within each site, and a consistent numbering scheme (VLAN 10 is always servers, VLAN 20 is always workstations) means any engineer can look at an IP address and immediately know which site, building, and function it belongs to. Route summarization becomes trivial because each site's addresses fall within a contiguous block. Firewall rules stay clean because the addressing scheme maps directly to security zones.

This tool generates the template that makes systematic planning practical. Instead of starting from a blank spreadsheet and deciding which columns to include, you get a pre-structured template with industry-standard fields, hierarchical site groupings, and output formats compatible with popular IPAM platforms. Fill in the template during the design phase, and you have a document that guides every subsequent configuration decision -- from router interfaces and DHCP scopes to DNS zones and monitoring dashboards.

How to Generate an IP Address Plan Template

1. Enter your parent network blocks (e.g., 10.0.0.0/8 or 172.16.0.0/12)
2. Define your organizational hierarchy -- sites, buildings, floors, or logical groupings
3. Select the columns to include: network, CIDR, VLAN, gateway, DHCP range, DNS, owner, description
4. Add any custom fields specific to your organization (cost center, change ticket, etc.)
5. Choose your export format -- CSV for spreadsheets or JSON for programmatic processing
6. Download the generated template

Address Plan Template Example

A generated template for a multi-site enterprise network:

CSV Export Output

site,network,cidr,subnet_name,vlan,gateway,dhcp_start,dhcp_end,dns,owner,notes
HQ,10.1.0.0,24,Servers,10,10.1.0.1,,,10.1.0.10,IT Ops,Static only
HQ,10.1.1.0,24,Office LAN,20,10.1.1.1,10.1.1.50,10.1.1.250,10.1.0.10,IT Ops,
HQ,10.1.2.0,24,Guest WiFi,30,10.1.2.1,10.1.2.10,10.1.2.250,8.8.8.8,Facilities,Isolated

When to Use the Address Plan Generator

• New network deployments -- create a structured plan before configuring any equipment
• IPAM migration -- generate templates compatible with phpIPAM, NetBox, and Infoblox for import
• Network audits -- build a comprehensive inventory template to document existing infrastructure
• Multi-site rollouts -- create consistent address plans across all locations with hierarchical site groupings
• Transitioning from ad-hoc documentation -- move from informal spreadsheets to a standardized format
• Cloud-hybrid planning -- include AWS VPCs, Azure VNets, and GCP networks alongside on-premises ranges

How IP Address Planning Works

A well-structured IP address plan assigns meaning to address space at every level of the hierarchy. This systematic approach prevents conflicts, simplifies routing, and makes networks self-documenting.

Hierarchical Address Allocation

Organize address space in nested blocks that mirror your network topology:

10.0.0.0/8          (Enterprise)
  10.1.0.0/16       (Headquarters)
    10.1.0.0/24     (HQ Servers)
    10.1.1.0/24     (HQ Office LAN)
    10.1.2.0/24     (HQ Guest WiFi)
  10.2.0.0/16       (Branch Office 1)
    10.2.0.0/24     (Branch-1 Servers)
    10.2.1.0/24     (Branch-1 Office LAN)
  10.3.0.0/16       (Branch Office 2)

This hierarchical model enables route summarization -- a single route like 10.1.0.0/16 advertises all HQ subnets to remote sites, keeping routing tables small and manageable.

Essential Columns in an Address Plan

• Network / CIDR -- the subnet address and prefix length
• Subnet Name -- human-readable purpose identifier
• VLAN ID -- the Layer 2 VLAN mapped to this subnet
• Default Gateway -- typically the first usable address (e.g., .1)
• DHCP Range -- start and end addresses for the dynamic pool
• DNS Servers -- primary and secondary resolver addresses
• Owner / Department -- responsible team for capacity and change management

Common Allocation Patterns

Building an Effective Address Plan

The most common mistake in address planning is skipping the hierarchy and assigning subnets on a first-come, first-served basis. When the New York office gets 10.1.0.0/24 and the next available block happens to be 10.47.3.0/24, you lose the ability to summarize routes for the entire site with a single prefix. Every subnet becomes an individual entry in your routing tables, your firewall rules grow to dozens of lines per site, and troubleshooting requires looking up each address in a spreadsheet rather than recognizing it from the second octet.

Start your plan by reserving contiguous blocks for each site before assigning individual subnets. Give headquarters 10.1.0.0/16, the first branch 10.2.0.0/16, and so on. Within each site block, establish a consistent VLAN numbering scheme: VLAN 10 for servers (always the first /24), VLAN 20 for office workstations, VLAN 30 for guest WiFi. This consistency means an engineer visiting any site immediately knows that 10.x.1.0/24 is the office LAN and 10.x.2.0/24 is guest WiFi, regardless of which site x represents.

Do not forget to include cloud networks in your plan. AWS VPCs, Azure VNets, and GCP networks consume private address space just like on-premises subnets, and if you connect them via VPN or Direct Connect they must not overlap with any existing ranges. Allocate cloud blocks from the same hierarchical scheme -- for example, 10.100.0.0/16 for the production VPC, 10.101.0.0/16 for the staging VPC -- so they integrate cleanly with your overall addressing architecture.

Frequently Asked Questions

What IPAM platforms can import the generated CSV?

The CSV format is compatible with phpIPAM (via CSV import), NetBox (via custom scripts or the netbox-csv-import plugin), Infoblox (CSV import job), and any spreadsheet tool like Excel or Google Sheets. Column headers follow common IPAM naming conventions for minimal mapping.

How should I allocate address space across multiple sites?

A common pattern assigns a /16 per site from a 10.0.0.0/8 private range. This gives each site 256 possible /24 subnets (65,534 hosts), enables clean route summarization, and provides ample room for growth. Smaller organizations may use /20 or /22 blocks per site from 172.16.0.0/12.

Should I include cloud VPCs in my address plan?

Yes. Cloud networks (AWS VPCs, Azure VNets, GCP VPCs) consume private address space and must not overlap with on-premises ranges, especially if you use VPN or Direct Connect/ExpressRoute. Include cloud allocations in your plan to prevent conflicts.

What if my organization uses multiple RFC 1918 ranges?

Many organizations use addresses from more than one private range (e.g., 10.0.0.0/8 for internal and 172.16.0.0/12 for lab environments). Include all ranges in your address plan to maintain a single source of truth. The Duplicate Subnet Detector can verify that allocations across different ranges do not overlap.

How do I handle acquired company networks?

During mergers and acquisitions, the acquired company's address space often overlaps with yours. Document both plans side by side, run a duplicate subnet check, and develop a renumbering strategy for the conflicting ranges before connecting the networks. The address plan template helps organize this migration systematically.

Related Tools

• VLSM Calculator - Calculate variable-length subnet allocations from host requirements
• Subnet Naming Convention Builder - Generate standardized subnet names from templates
• VLAN-to-Subnet Mapper - Map VLAN IDs to their corresponding subnets
• IPAM Import Formatter - Format data for specific IPAM system imports
• Duplicate Subnet Detector - Validate your address plan has no overlapping subnets