Scopes, Pools, and Reservations

DHCP would be chaos if it gave out random addresses with no rules. Administrators control it using three related ideas: scopes, pools, and reservations. Together they decide which addresses a network can use, which are free to lease, and which devices always get the same address. This lesson shows how each works and why they keep large networks organized and predictable.

A scope is the full range of addresses a DHCP server manages for one subnet, plus the settings that go with them. For example, a scope might cover 192.168.1.1 through 192.168.1.254 with a matching mask, gateway, and DNS. The scope defines the boundaries of what DHCP can hand out on that network. A server can hold several scopes, one per subnet it serves.

Within a scope, the pool is the set of addresses actually available to lease. The pool is usually narrower than the full scope because some addresses are set aside. For instance, the scope might be .1 to .254, but the pool that DHCP leases out could be .100 to .200, leaving the lower addresses for routers, servers, and printers configured manually.

An exclusion is an address or range inside the scope that DHCP must never lease. Suppose a server already uses 192.168.1.10 with a hand-set address. You exclude .10 so DHCP skips it and avoids a conflict. Exclusions are how you carve safe gaps into a scope for devices whose addresses are fixed outside of DHCP control.

A reservation ties a specific address to a specific device so that device always receives the same one. The server matches the device by its MAC address (Media Access Control address), the hardware identifier burned into its network card. When that device asks for an address, DHCP hands it the reserved one every time, giving the convenience of DHCP with the stability of a fixed address.

You could instead set a fixed address manually on the device itself, called a static assignment. A reservation differs because the address still comes from the DHCP server, so settings like gateway and DNS stay centrally managed. Change the DNS once on the server and reserved devices update automatically. Static addresses must be edited on each device by hand, which is easy to forget.

Reservations suit devices that need a stable address but should stay under DHCP control: network printers, IP cameras, point-of-sale terminals, and lab equipment. Users connect to a printer by address or name, so it should not change. A reservation guarantees consistency while letting the administrator manage everything from the DHCP server rather than visiting each device.

To create a reservation, the administrator records the device MAC address and binds it to a chosen IP inside the scope. From then on, DHCP recognizes that MAC and returns the matching address. The example below shows the kind of mapping an administrator defines on the server. The address still must fall within the scope and not collide with the active pool.

Pool size matters. If the pool holds 100 addresses but 150 devices need leases at once, some devices get nothing and fail to connect. Administrators size the pool to peak demand, sometimes shortening lease times in busy guest networks so addresses recycle faster. Reservations and exclusions reduce the usable pool, so plan the scope with all three in mind.

Large networks span many subnets, so one DHCP server often holds several scopes. A relay agent forwards requests from each subnet to the server, which selects the scope that matches the network the request came from. This central design means an administrator manages addressing for a whole campus from one place, with each scope tuned to its own subnet.

Think of it as nested control. The scope is the whole address range and settings for a subnet. The pool is the leasable portion. Exclusions carve out gaps for manually set devices. Reservations pin certain addresses to certain devices by MAC. Used together, they let DHCP be both automatic and orderly, exactly what a growing network needs.

Test your scope knowledge.

Administrators shape DHCP with three tools. A scope is the full address range and settings for a subnet. The pool is the leasable subset, often narrowed by exclusions that protect manually set addresses. A reservation binds a chosen address to a device by its MAC address, giving a stable IP that DHCP still manages, unlike a hand-set static address. One server can hold many scopes to serve a whole campus from a single point.