Course contentsShow
← Cloud and Infrastructure
Lesson 179 of 2,9894. Cloud Networking BasicsFree lesson

Reserved IP Addresses in Subnets

Learn which IP addresses are reserved by cloud providers in each subnet and why.

Reserved IP Addresses in Subnets

You'll learn why not every IP address in your subnet is actually available for use.

When you create a subnet in a virtual network, you might think all the IP addresses in that CIDR range are yours to assign. Surprise! Cloud providers automatically reserve several addresses in each subnet for essential network operations.

Why Some IPs Are Off-Limits

Think of a subnet like a city block of houses. The cloud provider reserves certain "addresses" for infrastructure—like the street sign post, the utility access panel, and the neighborhood mailbox. You can't build on those spots, even though they're technically on your block.

The Standard Reservations

Typically, four or five addresses are reserved in every subnet:

  1. Network address (first IP) - Identifies the subnet itself
  2. Router/gateway address (often second IP) - Where traffic exits the subnet
  3. DNS server address (often third IP) - For name resolution services
  4. Cloud provider reserved (often fourth IP) - For future cloud services
  5. Broadcast address (last IP) - Network broadcast operations

Practical Example

In a subnet with CIDR 10.0.1.0/24 (256 total addresses):

  • 10.0.1.0 - Network address ❌
  • 10.0.1.1 - Gateway/router ❌
  • 10.0.1.2 - DNS server ❌
  • 10.0.1.3 - Reserved ❌
  • 10.0.1.4 through 10.0.1.254 - Available for your use ✅
  • 10.0.1.255 - Broadcast address ❌

That leaves you with 251 usable addresses, not 256.

Key Takeaway: Always account for reserved IPs when planning subnet sizes—cloud providers automatically claim the first few and last addresses in every subnet for network infrastructure, reducing your usable capacity.