Subnet design is where arithmetic becomes engineering. A good design allocates enough addresses for each segment, leaves sensible room for growth, keeps broadcast domains manageable, supports route aggregation where useful, and aligns addressing with security and operational boundaries.
Remember the shape, not the sentence
“Pretend you are designing a campus with three buildings. You do not paint one enormous room and then draw imaginary walls; you create real zones that make movement, security and expansion easier.”
Requirements first
Count current hosts, expected growth, infrastructure addresses, special devices and point-to-point links before choosing prefixes.
Choose prefixes from largest need downward
Variable-length subnetting reduces waste. Allocate the largest subnet first so the address space does not get fragmented by small early allocations.
Route summarization
Contiguous prefixes can sometimes be summarized to reduce routing-table size. Good address planning therefore considers the routing system, not only endpoint counts.
See the mechanism before you memorize it
One diagram, one causal story, one reconstruction task.
Subnet 3 networks + design a small topology — causal map
Sales
Needs 90 hosts → choose the smallest practical subnet that satisfies growth.
Engineering
Needs 45 hosts → allocate a smaller VLSM prefix.
Infrastructure
Needs 12 hosts → use a compact subnet.
Validate
Check non-overlap, host capacity, gateways and future growth.
Draw the idea yourself
Rebuild the core flow on a real canvas before moving to the worked walkthrough.
Walk the system
Sales
Needs 90 hosts → choose the smallest practical subnet that satisfies growth.
Engineering
Needs 45 hosts → allocate a smaller VLSM prefix.
Infrastructure
Needs 12 hosts → use a compact subnet.
Validate
Check non-overlap, host capacity, gateways and future growth.
Summarize
Look for contiguous prefixes that can be advertised efficiently.
Design worksheet
The exact allocation depends on the available parent block and future growth. The important habit is to derive the prefix from the requirement rather than choosing a familiar mask first.
Need 90 hosts → /25 (126 conventional usable)
Need 45 hosts → /26 (62 conventional usable)
Need 12 hosts → /28 (14 conventional usable)
Then place them on non-overlapping boundaries.What usually goes wrong
Close the tab. Rebuild it from memory.
Read the question, answer aloud, then reveal.
Why allocate the biggest requirement first?Reveal answer
Large subnets are harder to fit after many smaller fragments have already consumed the address space.
What is VLSM?Reveal answer
Variable Length Subnet Masking: different subnets use different prefix lengths within a larger address block.
Why does address planning affect routing?Reveal answer
Hierarchical, contiguous allocations can improve route summarization and reduce the number of individual prefixes that routers must carry.
Make this idea travel.
Connect it next to: tcp-reliability • routing-protocols • dns.