What you need to know
How should a DHCP scope represent a subnet with addresses that must not be leased?
Potentially affected
Administrators planning Windows Server DHCP scopes and exclusions.
DSE recommendation
Prepare an address worksheet showing the overall scope and every intended exclusion.
Source facts
A DHCP scope groups addresses that a server can lease to clients on a subnet. Microsoft describes a single scope as an address range together with its configuration options. The Windows Server guidance permits one scope for a subnet, defined as one continuous address range. Administrators needing several usable ranges inside that subnet define the scope first and then add exclusion ranges. Microsoft documentation.
Applicability
Identify the subnet, proposed pool, existing address allocations, and reservations or exclusions already recorded. Review the addressing plan before enabling the scope, and ask the network owner to resolve conflicting inventory entries.
DSE recommendation
Prepare an address worksheet showing the overall scope and every intended exclusion. Name the owner of each address block and the reason it is excluded. Have a second reviewer compare the worksheet with the planned configuration and confirm the intended gateway and DNS options separately.
Verification
Use an approved client test to inspect the assigned address and options. Compare the server’s configured range and exclusions with the worksheet, then reconcile observed leases with the intended eligible addresses. Preserve any unexpected allocation as a finding for investigation before extending the scope to additional clients.
Official references
Microsoft Learn: DHCP scopes in Windows Server. Source reviewed September 8, 2026.
Review the official source
DHCP scopes in Windows Server · Verified September 8, 2026
Need help applying this guidance safely?
DSE can help confirm applicability, protect service continuity, and validate the result across physical security and IT systems.
Talk with DSE