DHCP Scopes and Reservations

A DHCP scope is defined by a start and end IP address, a subnet mask, and a lease duration, and it represents the full pool of addresses a server may hand out for one particular subnet. Within that pool, administrators typically carve out exclusion ranges, addresses that fall inside the scope's numeric range but should never be dynamically assigned, commonly used to reserve the low end of a subnet for static infrastructure like routers, switches, and printers. Lease duration matters too: a typical corporate LAN might use an 8-day lease since devices are relatively stable, while a guest Wi-Fi scope might use a much shorter lease, such as 1 hour, because devices churn constantly and short leases free up addresses faster.

A DHCP reservation ties a specific IP address, still drawn from within the scope's range, to a device's MAC address, so that device always receives the same address on every lease renewal while still benefiting from centralized DHCP management rather than requiring a manual static configuration on the device itself. Reservations are the right tool for devices that need a predictable address, like a network printer that other systems reference by IP, a VoIP phone integrated with a call manager, or a server that isn't yet ready for a fully static configuration. Unlike exclusions, which block an address from ever being handed out dynamically, reservations guarantee a specific device gets a specific address whenever it requests one.

Scope options configure the extra settings a client receives along with its address, the most common being Option 003 (Router/default gateway), Option 006 (DNS Servers), and Option 015 (DNS Domain Name); these can be set per-scope or inherited from server-level options that apply to every scope unless overridden. When a single physical subnet needs more addresses than one logical scope can provide, or when multiple logical IP subnets share the same physical wire, administrators combine two or more scopes into a superscope, which lets the DHCP server manage them as a single administrative unit while still enforcing each scope's own exclusions and options. Superscopes are also useful during a subnet renumbering migration, letting old and new address ranges coexist temporarily.