The address plan is the map everyone else uses
IP address documentation is the record of every prefix, VLAN, DHCP scope, reservation, static assignment, DNS zone and public address your business uses, with the purpose and owner of each. When it is current, a technician can place a new printer, troubleshoot a phone or add a site without guessing which address is safe.
When it is missing, the same problems repeat: a printer that drops off the network because someone gave it an address inside the DHCP range, a camera nobody can find, a VPN that will not route because both offices use the same subnet. Each one costs hours that a one-page plan would have saved.
The IP plan sits inside the wider network documentation and feeds the IT asset inventory: every device record carries an address that falls inside a documented subnet.

What complete IP address documentation includes
Eight parts, from the private prefix plan to the public addresses your ISP assigned.
| Part | What to record | Why it matters |
|---|---|---|
| Prefix plan | The summary block for each site (for example one /16 per site) and how it is divided, using the RFC 1918 private ranges 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16 | Sites and VPNs never overlap, and routing stays simple |
| VLANs | VLAN ID, name, purpose, subnet, gateway, the switches and SSIDs that carry it, and the security zone it belongs to | Anyone can tell what a VLAN is for before changing a port |
| DHCP scopes | Scope range, exclusions, lease time, DNS servers and options handed out, and which server or firewall runs DHCP | Dynamic and static addresses never collide |
| Reservations | MAC address, reserved IP, device name and the reason for the reservation | Printers, phones and imaging devices keep a predictable address |
| Static assignments | Every manually set address: network gear, servers, storage, cameras, controllers, with the owner | No more surprise conflicts from undocumented statics |
| DNS zones | Internal zones (for example the Active Directory domain), public zones, where each is hosted, who can edit it, and key records | Mail, websites and sign-ins do not break after a provider change |
| Public IPs and NAT | Public blocks from each ISP, which address maps to which internal service, and outbound NAT rules | Firewall changes and ISP moves are planned, not discovered |
| IPv6 (if used) | Assigned prefixes, how they are delegated per VLAN, and whether SLAAC or DHCPv6 is used | IPv6 traffic is documented and filtered, not invisible |
Sample IP and VLAN plan: Harborview Dental Group
The same practice shown on the network documentation page: one /16 per site, one /24 per VLAN, gateways on the firewall.
| VLAN | Name and purpose | Subnet | Gateway | Addressing | Notes |
|---|---|---|---|---|---|
| 10 | Clinical · operatory PCs, imaging sensors, printers | 10.20.10.0/24 | 10.20.10.1 | DHCP .100–.199 · printers reserved | 14 PCs · 3 imaging sensors · 2 printers |
| 20 | Front office · PCs, IP phones, check scanner | 10.20.20.0/24 | 10.20.20.1 | DHCP .100–.199 | Duplicate IP 10.20.20.45 flagged |
| 30 | Servers · practice management, backup, NAS | 10.20.30.0/24 | 10.20.30.1 | Static only | SRV-PM-01 .10 · NAS-BK-01 .20 |
| 40 | Guest Wi-Fi · internet only | 10.20.40.0/24 | 10.20.40.1 | DHCP .50–.250 · short lease | Isolated from VLANs 10–30 |
| 99 | Network management | 10.20.0.0/24 | 10.20.0.1 | Static only | FW-HQ-01 .1 · SW-CORE-01 .2 · SW-ACC-02 .12 · AP-OPS-03 .33 |
| 10 (second office) | Second office · combined LAN | 10.21.10.0/24 | 10.21.10.1 | DHCP .100–.199 | Reached over the site-to-site VPN |
Public side: a /29 from the fiber ISP gives five usable static addresses, each recorded in the circuit register with the internal service it maps to. All names, addresses and counts are fictional.
Four common IP addressing problems
None of these needs expensive tooling to fix. They need the plan written down and followed.
Overlapping subnets across sites and VPNs
Two offices, a home network and a vendor all on 192.168.1.0/24. Site-to-site and remote-access VPNs then need NAT workarounds that nobody remembers later. A prefix plan per site prevents it.
Undocumented static addresses
A technician set a camera or controller to a static IP inside the DHCP range years ago. One day DHCP hands that address to a laptop, and both devices drop off. Every static needs a record and a place outside the scope.
Duplicate IP addresses
Two devices claiming the same address cause intermittent faults that look like bad cables. Our inventory flags duplicates as soon as they are entered, like the 10.20.20.45 clash in the sample.
VLAN sprawl
VLANs added for one project and never removed, VLANs with no name, and trunks that carry every VLAN everywhere. Each unused VLAN is attack surface and confusion. The plan lists what exists and why.
Spreadsheet or IPAM tool: choosing a home for the IP plan
The right tool depends on size and how often addresses change. We work in whatever platform you already use.
| Approach | Works well when | Watch for |
|---|---|---|
| Spreadsheet | One or two sites, a few hundred addresses, a small team | Goes stale fast; no link to live DHCP data; version confusion when copied |
| NetBox (open source, with commercial editions from NetBox Labs) | You want a network source of truth for prefixes, VLANs, VRFs, racks, cabling and circuits | Needs an owner to keep it updated or integrated with automation |
| Discovery-based IPAM (for example Device42) | You want addresses found automatically alongside a CMDB and dependency maps | Freshworks is moving Device42 capabilities into Freshservice IT Asset Management through 2026 and early 2027; plan around the transition |
| DDI platforms (for example Infoblox) | DNS, DHCP and IPAM are run together across many sites | Designed for multi-site environments; purpose and owner fields still need filling in |
| Documentation platform fields (IT Glue, Hudu, SharePoint) | The rest of your documentation already lives there | Address data is manual unless synced from another source |
For a side-by-side view of documentation platforms, see IT documentation software compared. Vendor names are trademarks of their owners; OC Security Audit is independent of every vendor named.
DHCP logs, DNS and change records keep the plan honest
An IP plan drifts the moment someone plugs in a new device. Three data sources pull it back.
DHCP logs. CIS Controls v8.1 Safeguard 1.4 calls for DHCP logging on all DHCP servers or IP address management tools, used to update the enterprise asset inventory, with logs reviewed at least weekly. A new MAC address in the lease table is a new device to identify and record.
DNS records. Forward and reverse records that match the plan make devices easy to find and stale entries easy to spot. Document who can edit each zone; a public DNS change can take down mail or a website.
Change records. Reserve the address in the plan before you assign it, not after. Each change that adds a subnet, VLAN or static IP updates the plan as a step in the record. Our IT change management page shows the format.
Get your IP address documentation reviewed or built
In an IT Documentation Audit we compare your existing IP plan with the live DHCP, DNS and switch data and report every gap, conflict and overlap. In an IT Documentation Build we create the plan with you, linked to the network diagram, the WAN circuit register and the device inventory. Each package is $3,500 fixed, one-time; details are on the IT documentation pricing page.
We work on-site across Orange County and Southern California from Irvine, and remotely nationwide. Our work is read-only. If renumbering or VLAN cleanup is needed, IT Perfection can carry it out. For a broader security view of the internal network, see our internal security audit.

Where to go next
WAN and ISP circuit documentation
Circuit IDs, static blocks, SLAs, VPN peers and failover records for every connection that leaves the building.
Firewall configuration documentation
Rule base, NAT and VPN records with a business reason and owner for every rule.
Page 5 of 22: IP address and VLAN documentation
- 1. IT documentation services (hub)
- 2. Why IT documentation matters
- 3. What to include in IT documentation
- 4. Network documentation
- 5. IP address and VLAN documentation (this page)
- 6. WAN and ISP circuit documentation
- 7. Firewall and network settings documentation
- 8. Cloud documentation: Microsoft 365, Azure, AWS
- 9. Data-flow diagrams
- 10. IT asset inventory
- 11. IT password documentation
- 12. IT change management
- 13. Runbooks and disaster-recovery documentation
- 14. Securing your IT documentation
- 15. IT documentation for compliance
- 16. IT documentation software compared
- 17. Configuration backup and change tools
- 18. How to document a network
- 19. IT documentation checklist
- 20. Sample IT documentation package
- 21. IT documentation audit
- 22. IT documentation pricing

Guided by Ali Hassani, CISO
Certified CISO (C|CISO) and CISSP with 25+ years in IT, cybersecurity, compliance and infrastructure, and dozens of Microsoft and Cisco certifications, including MCSE, MCITP, MCSA Security, CCNP and CCNA. Ali checks every subnet in the plan against live DHCP and switch data before it is handed over, so the plan starts out accurate.
Questions about IP address documentation
What is the difference between an IP plan and IPAM?
The IP plan is the design: which prefixes, VLANs and scopes exist and why. IPAM is software that stores and tracks those addresses. A small office can keep the plan in a spreadsheet; larger networks benefit from an IPAM tool.
Should we renumber our network if both offices use 192.168.1.0/24?
If the sites need to talk to each other over a VPN, usually yes, and it is easier before the next site or merger. We document the current state and a target plan; the renumbering itself is hands-on work for your IT team or IT Perfection.
Do printers and phones need DHCP reservations or static IPs?
Either works if it is documented. Reservations keep control in one place and avoid typing errors; statics should sit outside the DHCP range and appear in the plan with an owner.
Do we need to document IPv6 if we do not use it?
Record whether IPv6 is enabled on your firewall, ISP circuits and clients. Many devices use it by default, so an undocumented IPv6 path can bypass rules written only for IPv4.
How often should the IP plan be reviewed?
Update it with every change that adds a subnet, VLAN or static address, and reconcile it against DHCP and switch data on a set schedule. CIS Safeguard 1.4 suggests reviewing DHCP logs at least weekly for inventory purposes.
Implementation partner
OC Security Audit documents and audits; it stays independent of the administration of your systems. If you want hands-on work, IT Perfection can fix what the documentation uncovers and keep the records current as part of managed IT.

Know which address is safe to use, every time
Send us your site count and the IP records you have today. Schedule a consultation and we will scope the work on a 30-minute call.
Irvine, Orange County and Southern California on-site; remote nationwide. Fixed one-time price: $3,500.


