What is a DHCP exclusion?
An exclusion carves addresses out of a scope. The scope still covers the whole range, but the server skips the excluded addresses when it makes offers. Administrators use exclusions to protect addresses that are typed in by hand on the device itself, such as the router interface, servers, network printers, access points and managed switches.
Why exclusions matter
A DHCP server only knows about the addresses it has leased. If a printer is set by hand to 192.168.1.50 and that address sits inside the scope with no exclusion, the server may later lease .50 to a laptop. The result is an IP address conflict: Windows warns that another device on the network is using the address, and one or both devices lose connectivity on and off. Excluding .50, or the whole block that static devices use, prevents it.
Exclusion vs. reservation
| Question | Exclusion | Reservation |
|---|---|---|
| What the server does | Never offers the address | Offers the address only to one client |
| How the device gets its address | Static IP configured on the device | DHCP, matched by MAC address |
| Where the settings live | On each device | On the DHCP server |
| Changing the gateway or DNS | Edit every device by hand | Update the DHCP options once |
| Typical use | Routers, servers and infrastructure that must work even if DHCP is down | Printers, cameras and NAS units that need a predictable address |
Configuring exclusions
- Windows Server: in the DHCP console, open the scope, right-click Address Pool and choose New Exclusion Range, then enter a start and end address (use the same address in both fields for a single IP). The New Scope Wizard also has a page for exclusions.
- SOHO routers: most have no exclusion list. You get the same effect by setting the DHCP start and end addresses so static devices fall outside the pool, for example static devices on .2 to .99 and DHCP on .100 to .199.
- Split scopes: when two servers share one subnet for redundancy, each server excludes the part of the range that the other server hands out.
Planning a subnet
A simple plan for a /24 network keeps the low addresses for infrastructure (gateway, switches, access points, servers), a block for printers and other devices that need fixed addresses, and the rest for the DHCP pool. Writing the plan down and matching it with exclusions (or a pool that starts above the static block) keeps static and dynamic addresses from overlapping as the network grows.
Troubleshooting cues
- "Windows has detected an IP address conflict" after a printer or server was given a static address: check that the address is excluded or outside the scope.
- A new scope fills up faster than expected: large exclusion ranges shrink the usable pool.
- A device with a reservation still gets a different address: the MAC address in the reservation may be wrong, for example a laptop that connected over Wi-Fi instead of Ethernet, which has a different MAC address.
DHCP exclusion on the CompTIA A+ exam
Exclusions is a bullet under DHCP in Core 1 objective 2.4, next to scope, leases and reservations. The exam likes to contrast exclusions with reservations: an exclusion keeps an address out of the pool so it can be assigned statically, while a reservation makes DHCP give one device the same address every time. If a question says a statically addressed device conflicts with DHCP clients, the fix is an exclusion (or moving the static address outside the scope). If it says a device should keep the same address but stay on DHCP, the answer is a reservation.