Basic Subnetting (for DHCP Scopes)

You don’t need to be a subnetting wizard to run DHCP—but you do need a clean mental model of what a subnet is and what addresses are valid inside it. This page is a DHCP-focused primer that connects subnetting directly to scopes, pools, and common “DHCP is broken” symptoms.

After this page, you should be able to:

Explain the idea of network vs host bits (CIDR/subnet mask boundary)
Identify network, broadcast, and usable host ranges for a simple subnet
Validate whether a DHCP scope actually matches the client subnet/VLAN
Recognize when “got an IP but nothing works” is a subnet/options problem
Verify client subnet settings quickly using Windows commands

Minimal Mental Model: IP = Network + Host

An IPv4 address has two parts: a network portion (which subnet you’re on) and a host portion (which device you are inside that subnet). The subnet mask / CIDR prefix tells you where the boundary is.

Example: 10.10.20.0/24 means “the first 24 bits identify the network.” In a /24, the last 8 bits are host bits, so you have \(2^8\) total addresses.

What’s Valid Inside a Subnet?

Every subnet has three categories of addresses: the network address, the broadcast address, and the usable host range.

Network address

Identifies the subnet itself (not assignable to a host).

Broadcast address

Reaches all hosts in the subnet (not assignable to a host).

Usable hosts

The addresses you can assign to devices (or lease via DHCP).

Why DHCP cares:

DHCP pools must only include usable host addresses. If you put the network or broadcast address in a pool (or hand out addresses that don’t fit the subnet), clients will behave unpredictably and troubleshooting becomes a mess.

Why Subnetting Matters to DHCP Scopes

A DHCP scope is “the rule set for one subnet.” If the subnet definition doesn’t match the actual VLAN/L3 segment, clients will either fail to get an offer or get configuration that looks fine but doesn’t work.

Quick mapping example:

Client VLAN/Subnet: 10.10.20.0/24
Default gateway (SVI/router): 10.10.20.1
Scope subnet: 10.10.20.0 with mask 255.255.255.0
Pool: valid 10.10.20.x host addresses (not .0 or .255)

Quick Cheat Sheet: Common Sizes

You don’t need to memorize everything—just recognize common prefixes and rough capacity. A useful high-level formula is: usable hosts = 2^(host bits) - 2.

/24 → ~254 usable hosts
/25 → ~126 usable hosts
/26 → ~62 usable hosts
/27 → ~30 usable hosts

Worked Example (One Only): 10.10.20.0/24

For a /24, the host portion is the last octet. That means the subnet spans from 10.10.20.0 to 10.10.20.255.

Identify the key addresses:

Network: 10.10.20.0
Broadcast: 10.10.20.255
Usable hosts: 10.10.20.1 – 10.10.20.254

Propose a DHCP-friendly pool design:

Gateway / Infra: 10.10.20.1 - 10.10.20.49
DHCP Pool:       10.10.20.50 - 10.10.20.199
Reserved Growth: 10.10.20.200 - 10.10.20.254

The exact cut lines vary, but the idea stays the same: keep infrastructure stable and keep the dynamic pool out of that space.

Troubleshooting Lens: What You Observe → What It Usually Means

“Discover but no Offer” / renew hangs

What you observe: Client can’t get a lease (may fall back to 169.254.x.x).

What it usually means: No matching scope for that subnet, scope disabled, DHCP relay missing, or DHCP server unreachable.

Wrong subnet mask

What you observe: Local devices sometimes reachable, off-subnet routes fail, “weird” connectivity.

What it usually means: Client thinks the network is larger/smaller than it really is, so it ARPs for things it should route (or routes things it should ARP).

Wrong default gateway

What you observe: Client can talk to local hosts but can’t reach other subnets/internet.

What it usually means: DHCP option points to a non-existent gateway or the wrong VLAN’s gateway.

Overlapping subnets / conflicting scopes (high level)

What you observe: Intermittent routing, duplicate address behavior, clients get “valid-looking” addresses that don’t belong.

What it usually means: Two networks are using overlapping IP space, or scopes/pools were created without a clean IP plan.

IP conflicts due to pool design

What you observe: Random drops and “duplicate IP” symptoms.

What it usually means: Static devices are living inside the dynamic pool; the pool doesn’t clearly separate infrastructure from clients.

Hands-on: Verify Subnet Settings on Windows

Check what you actually received:

ipconfig /all

Inspect: IPv4 Address, Subnet Mask, Default Gateway, DNS Servers, and DHCP Server.

Quick sanity test (optional):

ping <default-gateway-ip>
route print

If you can’t ping the gateway, you’re not “on the subnet” in any meaningful way—fix L2/VLAN, IP/mask, or gateway first.

Want the Full Subnetting Skill?

This DHCP page is intentionally a lightweight bridge. If you want a complete, step-by-step subnetting course (2–3 hours, beginner → intermediate), jump into the full lab.

Go deeper: binary fundamentals, CIDR, host ranges, VLSM, and real-world design practice.

Open Subnetting 101 →

Key Takeaways

Subnetting defines what addresses are valid inside a VLAN/L3 segment.
Network and broadcast addresses aren’t assignable; DHCP pools should use only usable hosts.
Scopes must match the subnet (network + mask) or clients will fail to lease or won’t work correctly.
Wrong mask/gateway creates “weird” failures that look like random outages.
Pool design matters: keep infrastructure stable and out of the dynamic range.
Verify from the client first: ipconfig /all shows IP/mask/gateway/DNS/DHCP server.

If subnetting still feels fuzzy, that’s normal—it’s a skill you build with reps. Use the full Subnetting 101 lab to get confident, then come back and your DHCP scope design will feel easy.