DHCP Scope Calculator: Pool Range, Size and Lease Time

How to use this DHCP scope calculator

1. Choose a mode: check a deployed start/end range or size a new scope.
2. Enter the network: supply an IPv4 network address or CIDR; existing-scope mode also needs the pool start and end.
3. Add the default demand inputs: peak or active clients, lease duration, and growth buffer.
4. Refine if needed: open Advanced sizing for exclusions, pool reservations, modeled clients, churn, target utilization, and network profile.
5. Review and implement carefully: use the recommendation, capacity segments, detailed arithmetic, lease guidance, and optional configuration draft.

DHCP scope concepts

Subnet

The address block defined by a network address and prefix or mask.

DHCP scope

The server's administrative address and option grouping for clients on a subnet.

Dynamic pool

The inclusive start-to-end range available for allocation; it does not have to cover the whole usable subnet.

Exclusion

An address inside the configured scope range that the DHCP server must not dynamically assign.

Reservation

An address associated with a particular client. It reduces general assignable capacity when it is inside the pool and not already counted as excluded.

Active lease

An address currently recorded as leased, which may include a client that has already left.

Utilization

Leases or projected demand divided by assignable pool capacity.

Annotated /24 example: a scope can be smaller than the subnet.

Formula and assumptions

Inclusive pool: end IP integer - start IP integer + 1

Assignable pool: inclusive pool - exclusions inside pool - reservations consuming pool capacity

Stale transient pressure: arrivals/day × max(lease hours - visit hours, 0) / 24

Modeled demand: steady clients + stale transient pressure

Planning basis: max(observed peak, modeled demand)

Projected leases: planning basis × (1 + growth buffer)

Required assignable pool: ceil(projected leases / target utilization)

The 80% target and profile lease ranges are configurable planning assumptions. IPv4 boundaries and inclusive range counts are deterministic arithmetic. T1 and T2 are shown at the RFC defaults of 50% and 87.5% only when a server does not provide other values.

Worked DHCP calculations

Office /24 that should expand to /23

A /24 has 2^8 = 256 total and 256 - 2 = 254 usable addresses. Suppose 30 pool addresses are exclusions or reservations and the larger of observed or modeled demand is 185 leases. Add 20% growth: 185 × 1.20 = 222 projected leases. At an 80% target, the assignable pool must be ceil(222 / 0.80) = 278. Restore the 30 unavailable pool addresses: 278 + 30 = 308 gross pool addresses. A /24 cannot fit 308 pool addresses, while a /23 has 510 usable addresses, so /23 is the smallest suitable common subnet.

Guest Wi-Fi where a shorter lease reduces stale holds

Assume 120 steady clients, 240 arrivals per day, and a 4-hour average visit. With a 24-hour lease, stale pressure is 240 × (24 - 4) / 24 = 200 addresses, for 320 modeled leases. With an 8-hour lease, it becomes 240 × (8 - 4) / 24 = 40, for 160 modeled leases. The shorter lease releases about 160 stale holds sooner, but it also produces more renewal traffic and must be tested against real client behavior.

IPv4 capacity and lease strategy tables

These are starting points, not universal standards. Pools can cover only part of the usable subnet.

Standards, sources, and review

Standards-based arithmetic is kept separate from planning choices. Network/broadcast boundaries and inclusive IPv4 range counts are mathematical; T1/T2 defaults come from DHCPv4. Target utilization, churn retention, and lease-profile ranges are adjustable operational assumptions that should be checked against logs.

• RFC 2131: Dynamic Host Configuration Protocol — DHCPv4 lease behavior and default T1/T2 fractions.
• Microsoft Learn: DHCP scopes in Windows Server — scope, exclusion, and reservation terminology.
• ISC Kea Administrator Reference: DHCPv4 server — subnet, pool, and valid-lifetime configuration.

Methodology author: Starlight Robotics infrastructure tooling team. Technical review: protocol behavior checked against RFC 2131 and vendor documentation. Reviewed: 18 July 2026.

FAQs

What is a DHCP scope?

A DHCP scope is the administratively defined set of IPv4 addresses and options a DHCP server can use for clients on a subnet. Its dynamic pool may cover only part of the subnet's usable range.

How do I calculate a DHCP start and end range?

Find the network and broadcast addresses from the CIDR, choose a start and end inside the usable host range, and count the pool inclusively as end minus start plus one. Then subtract only exclusions and capacity-consuming reservations inside that pool.

How many DHCP addresses are in a /24?

A /24 contains 256 total IPv4 addresses and normally 254 usable host addresses. The DHCP pool can be smaller because it may use only part of that usable range and can contain exclusions or reservations.

Do reservations reduce pool size?

A reservation inside the configured dynamic pool consumes one pool address when that reserved client holds it. A reservation or static address outside the pool does not reduce that pool, and an address already counted as excluded must not be subtracted again.

What causes DHCP scope exhaustion?

Common causes include too small a pool, growth, device churn combined with long leases, abandoned leases, excessive exclusions or reservations, unexpected clients, and overlapping or incorrect scope configuration.

What lease time should guest Wi-Fi use?

Four to twelve hours is a useful starting range for many guest networks, but the correct value depends on visit duration, daily churn, renewal traffic, and authentication policy. Validate it with lease history and client behavior.

Can two DHCP scopes overlap?

Two independently allocating scopes must not offer the same address range. Deliberate failover or split-scope designs require coordinated, non-conflicting allocation rules; accidental overlap can produce duplicate-address conflicts.

What are DHCP T1 and T2 renewal times?

Common DHCPv4 defaults are T1 at 50 percent of lease time and T2 at 87.5 percent of lease time unless the server provides different timers.

Does this calculator support DHCPv6?

No. This tool is for IPv4 DHCP scope planning. IPv6 address assignment usually uses different assumptions and much larger address spaces.

Is this calculator private?

Yes. Inputs are processed locally in your browser and are not sent to a server.

Disclaimer

This is an infrastructure planning aid. Validate DHCP scope changes with IPAM ownership, routing, firewall rules, relay configuration, DHCP failover design, and operational change-management requirements before applying them in production.