For IT leaders
Subnetting is foundational; if your team cannot do it from memory, every cloud, network, and firewall task gets slower and riskier.
Why IT teams care
Where this shows up at the team level
- Cloud landing zones, on-prem networks, and VPN designs all start with subnet planning.
- Mergers and acquisitions hit teams that did not plan for non-overlapping address space; remediation is painful.
- Help desk and junior network staff need fluency in subnetting before they can troubleshoot effectively.
In production
Where teams encounter it
- Designing VPC / VNet address spaces in AWS, Azure, and Google Cloud
- Sizing access, server, and management subnets on campus networks
- Reading firewall rules and route tables that use CIDR notation
How it works
How Subnetting and CIDR actually works
- 01An IPv4 address is 32 bits long; the subnet mask marks the boundary between network bits and host bits.
- 02CIDR notation writes the mask as a slash followed by the number of network bits, e.g. 10.10.10.0/24 means 24 network bits and 8 host bits.
- 03Borrowing more bits for the network creates more, smaller subnets; releasing bits creates fewer, larger subnets.
- 04Routers forward packets by matching the destination address against the longest matching prefix in the routing table.
In practice
Common team use cases
- Carving a /16 cloud VPC into smaller /24 subnets per environment
- Designing campus networks with one VLAN/subnet per user group
- Building summarized routes that keep the routing table small
Build the capability
Related CBT Nuggets training
Each link routes to a hub that goes deeper than this definition.
Related concepts