IP address documentation for every subnet, VLAN and static IP — OC Security Audit
IP address documentation

IP address documentation for every subnet, VLAN and static IP

One plan that shows each prefix, VLAN, DHCP scope, reservation and static address, who uses it and why, and matches what the network is really doing.

Stop overlapping subnets before they break a VPN — OC Security Audit
Before the next site or VPN

Stop overlapping subnets before they break a VPN

Two offices on 192.168.1.0/24 cannot be joined cleanly. A documented prefix plan catches the clash before the tunnel goes in.

Pick the right home for your IP plan, then keep it honest — OC Security Audit
Spreadsheet or IPAM

Pick the right home for your IP plan, then keep it honest

A spreadsheet works for one site. Larger networks need IPAM. Either way, DHCP logs and change records keep it current.

25+ yearsIT & cybersecurity experience
Certified expertsCISSP · C|CISO · Microsoft · Cisco
Southern CaliforniaLocal and on-site, based in Irvine
NationwideRemote documentation & audits
Why it matters

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.

Two network engineers with laptops comparing IP address records in a server aisle
What to record

What complete IP address documentation includes

Eight parts, from the private prefix plan to the public addresses your ISP assigned.

PartWhat to recordWhy it matters
Prefix planThe 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/16Sites and VPNs never overlap, and routing stays simple
VLANsVLAN ID, name, purpose, subnet, gateway, the switches and SSIDs that carry it, and the security zone it belongs toAnyone can tell what a VLAN is for before changing a port
DHCP scopesScope range, exclusions, lease time, DNS servers and options handed out, and which server or firewall runs DHCPDynamic and static addresses never collide
ReservationsMAC address, reserved IP, device name and the reason for the reservationPrinters, phones and imaging devices keep a predictable address
Static assignmentsEvery manually set address: network gear, servers, storage, cameras, controllers, with the ownerNo more surprise conflicts from undocumented statics
DNS zonesInternal zones (for example the Active Directory domain), public zones, where each is hosted, who can edit it, and key recordsMail, websites and sign-ins do not break after a provider change
Public IPs and NATPublic blocks from each ISP, which address maps to which internal service, and outbound NAT rulesFirewall 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 usedIPv6 traffic is documented and filtered, not invisible
Sample

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.

SAMPLE · Harborview Dental Group (fictional company) · illustrative data
VLANName and purposeSubnetGatewayAddressingNotes
10Clinical · operatory PCs, imaging sensors, printers10.20.10.0/2410.20.10.1DHCP .100–.199 · printers reserved14 PCs · 3 imaging sensors · 2 printers
20Front office · PCs, IP phones, check scanner10.20.20.0/2410.20.20.1DHCP .100–.199Duplicate IP 10.20.20.45 flagged
30Servers · practice management, backup, NAS10.20.30.0/2410.20.30.1Static onlySRV-PM-01 .10 · NAS-BK-01 .20
40Guest Wi-Fi · internet only10.20.40.0/2410.20.40.1DHCP .50–.250 · short leaseIsolated from VLANs 10–30
99Network management10.20.0.0/2410.20.0.1Static onlyFW-HQ-01 .1 · SW-CORE-01 .2 · SW-ACC-02 .12 · AP-OPS-03 .33
10 (second office)Second office · combined LAN10.21.10.0/2410.21.10.1DHCP .100–.199Reached 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.

What goes wrong

Four common IP addressing problems

None of these needs expensive tooling to fix. They need the plan written down and followed.

01

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.

02

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.

03

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.

04

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.

Where to keep it

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.

ApproachWorks well whenWatch for
SpreadsheetOne or two sites, a few hundred addresses, a small teamGoes 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 circuitsNeeds 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 mapsFreshworks 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 sitesDesigned 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 thereAddress 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.

Keeping it current

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.

How we help

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.

Laptop showing network monitoring graphs beside patch cabling
Related

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.

Ali Hassani, CISO, OC Security Audit
CISO-led

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.

FAQ

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.

IT Perfection managed IT
Two technicians in a data center aisle after documenting a network

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.