IP Reservation Table Builder

Build static IP assignment tables

MAC Format:
IP AddressMAC AddressHostnameDescription

Usage

Enter IP addresses and MAC addresses for each DHCP reservation. MAC addresses can be entered in any format (with or without separators). Export as CSV for documentation, or copy in dhcpd.conf or PowerShell format for direct server configuration.

The IP Reservation Table Builder creates comprehensive documentation of static IP address assignments, including device hostname, MAC address, IP address, purpose, and administrative notes. Enter your subnet (e.g., 10.1.10.0/24), add devices with their MAC and IP, and the tool validates entries, detects duplicate IP or MAC assignments, and exports DHCP reservation configurations for Windows Server, ISC DHCP, Cisco IOS, or CSV.

Understanding IP Reservations

Every network has devices that need a consistent, predictable IP address. Domain controllers, file servers, database servers, printers, access points, IP cameras, and management interfaces all rely on their addresses staying the same across reboots, power cycles, and network changes. If a domain controller's IP changes, every workstation that points to it for DNS loses resolution. If a printer's IP changes, every print queue in the organization breaks. These devices need stable addressing, and there are two ways to achieve it: static configuration or DHCP reservations.

Static configuration means setting the IP address directly on the device's network interface. It is simple and works everywhere, but it creates a management burden that grows with every device. When you need to change the DNS server address for fifty statically configured servers, you have to touch each one individually. When a server's NIC is replaced, the new hardware works immediately but is now outside your DHCP server's visibility. DHCP reservations solve this by tying an IP address to a specific MAC address on the DHCP server. The device still uses DHCP to obtain its address, but it always gets the same one. You manage the assignment centrally, and changes to DHCP options like DNS servers propagate automatically.

Regardless of which approach you use, the reservation table is the authoritative record of who has what address and why. Without it, engineers waste time running nmap scans to figure out what is using an address before they can safely assign it to a new device. This tool builds that record systematically, validates it against the subnet boundaries, catches duplicates before they cause conflicts, and exports it in the format your DHCP platform needs.

How to Build an IP Reservation Table

  1. Choose your subnet (e.g., 10.1.10.0/24) to scope the reservation table
  2. Add entries with hostname, MAC address, IP address, device type, and description
  3. The tool validates MAC formats, checks IPs against the subnet range, and detects duplicate IP or MAC assignments
  4. Import existing data from CSV files exported from network scans, inventory systems, or spreadsheets
  5. Export the table in your target DHCP platform's format -- Windows Server, ISC DHCP, Cisco IOS, or CSV

IP Reservation Table Example

Subnet: 10.1.10.0/24 -- Server VLAN

HostnameMAC AddressIP AddressTypeLocationOwnerNotes
dc0100:50:56:A1:23:4510.1.10.10Domain ControllerRack A3-U12IT OpsPrimary AD/DNS
dc0200:50:56:A1:23:4610.1.10.11Domain ControllerRack B3-U12IT OpsSecondary AD/DNS
file0100:50:56:A1:34:7810.1.10.20File ServerRack A3-U14IT OpsSMB shares
db0100:50:56:A1:45:9A10.1.10.30Database ServerRack A3-U16DBA TeamPostgreSQL primary
print0100:1B:A9:12:CD:EF10.1.10.50Network PrinterFloor 3 Copy RoomFacilitiesHP LaserJet
ap-fl3-01AC:67:B2:33:44:5510.1.10.60Access PointFloor 3 CeilingNetEngCisco 9120

Platform-Specific Export

Windows Server DHCP (PowerShell):

Add-DhcpServerv4Reservation -ScopeId 10.1.10.0 -IPAddress 10.1.10.10 -ClientId "005056a12345" -Name "dc01" -Description "Primary AD/DNS"
Add-DhcpServerv4Reservation -ScopeId 10.1.10.0 -IPAddress 10.1.10.11 -ClientId "005056a12346" -Name "dc02" -Description "Secondary AD/DNS"
Add-DhcpServerv4Reservation -ScopeId 10.1.10.0 -IPAddress 10.1.10.20 -ClientId "005056a13478" -Name "file01" -Description "SMB shares"

ISC DHCP (dhcpd.conf):

host dc01 {
    hardware ethernet 00:50:56:A1:23:45;
    fixed-address 10.1.10.10;
}
host dc02 {
    hardware ethernet 00:50:56:A1:23:46;
    fixed-address 10.1.10.11;
}
host file01 {
    hardware ethernet 00:50:56:A1:34:78;
    fixed-address 10.1.10.20;
}

Validation and Conflict Detection

The builder catches common data entry errors:

Validation CheckExample Flagged
Duplicate IP10.1.10.10 assigned to both dc01 and web01
Duplicate MAC00:50:56:A1:23:45 used for both dc01 and dc03
IP outside subnet10.1.11.10 does not belong to 10.1.10.0/24
Invalid MAC format00:50:56:ZZ:23:45 contains invalid hex characters
Reserved address10.1.10.0 (network) or 10.1.10.255 (broadcast)

When to Use the IP Reservation Table Builder

  • Initial server deployment -- document all static assignments before going live
  • DHCP reservation setup -- generate platform-ready configurations from a single source of truth
  • Network audits -- cross-reference reservations against actual device assignments
  • DHCP server migration -- export reservations from one platform and import into another
  • Asset tracking -- tie network addressing to physical asset inventory by hostname, location, and owner

How DHCP Reservations Differ from Static IPs

A static IP is configured directly on the device's network interface. A DHCP reservation is configured on the DHCP server to always assign the same IP to a specific MAC address. The device still uses DHCP, but gets a predictable address every time.

Static IP vs. DHCP Reservation Comparison

AspectStatic ConfigurationDHCP Reservation
Configuration locationOn each deviceCentralized on DHCP server
DNS/gateway updatesMust update each device manuallyPush changes from DHCP server
Device replacementReconfigure new deviceUpdate MAC in reservation
Management overheadHigh for many devicesLow -- single management point

DHCP reservations are preferred for most environments because they centralize address management while ensuring consistent assignments.

Maintaining Accurate Reservation Records

The hardest part of IP reservation management is not building the initial table -- it is keeping it accurate over time. Servers get decommissioned, printers get replaced, access points move to different locations, and virtual machines are cloned. If the reservation table is not updated when these changes happen, it gradually drifts from reality. Within a year, you may find that half the entries reference devices that no longer exist, and several active devices have addresses that do not appear in the table at all.

Build a habit of updating the reservation table as part of every change management process. When a new server is deployed, the change ticket should include adding the reservation. When a device is decommissioned, removing the reservation should be part of the decommission checklist. If your organization uses an IPAM system like NetBox or phpIPAM, the reservation table can be imported and maintained there, making it part of a larger asset management workflow rather than a standalone document that gets forgotten.

For existing networks that have no reservation table, the fastest way to build one is to combine data from multiple sources. Export the DHCP server's active leases and reservations. Pull the ARP table from your core switch or router (show arp on Cisco IOS). Run an nmap or arp-scan sweep of each subnet. Import all of these into the builder, let the validation catch duplicates and format issues, and then add the missing metadata (hostname, purpose, owner) manually. It takes an afternoon to document a medium-sized network, but the time investment pays for itself the first time you avoid a conflict.

Frequently Asked Questions

What MAC address format should I use?

The tool accepts both colon-separated (00:50:56:A1:23:45) and hyphen-separated (00-50-56-A1-23-45) formats, as well as bare hex (005056A12345). All formats are normalized to match your target DHCP platform's requirements during export.

Can I import reservations from a network scan?

Yes. Tools like nmap, arp-scan, or your switch's ARP table output can be exported to CSV. Import the CSV into the builder, add any missing fields (purpose, owner), and export for your DHCP platform. This is the fastest way to document an existing network.

How many reservations can a DHCP scope handle?

Windows Server DHCP and ISC DHCP can handle thousands of reservations per scope without performance issues. Practical limits are usually around available address space rather than server capacity. A /24 scope can have up to 253 reservations (254 usable addresses minus the gateway).

Should I use reservations or static IPs for servers?

DHCP reservations are preferred for most servers because they centralize address management. However, some environments require static configuration for critical infrastructure like domain controllers and DHCP servers themselves (a DHCP server cannot obtain its own address via DHCP). In practice, many organizations use static IPs for the two or three most critical servers and DHCP reservations for everything else.

How do I handle virtual machine clones?

VM cloning copies the source VM's MAC address by default, which creates a duplicate MAC conflict. Most hypervisors (VMware, Hyper-V, KVM) can generate a new MAC during cloning. After cloning, update the reservation table with the new MAC and assign a new IP address. The Duplicate IP Detector can catch cloning-related conflicts if the reservation table was not updated.

Related Tools

IPparse•Free Network & Subnet Calculator Tools

© 2026 IPparse. All tools run locally in your browser.

100% Privacy-First • No Data Collected