What Is a Reserved IP Address?

A reserved IP address is an address set aside for a particular use. In a cloud service, it usually means an address retained for your account so you can use it with an eligible resource. On a local network, it often means an address that DHCP consistently assigns to a particular device.

The term also appears in discussions of address ranges set aside for special purposes. These meanings are related, but they do not provide the same capabilities.

The three common meanings of reserved IP

When reading a provider’s documentation, first establish which meaning applies. A private range reserved by a standard is not a cloud address that you can reserve exclusively for your company.

How does a reserved IP work in a cloud?

In the common cloud model, an address exists as a separately managed resource. You reserve it, associate it with an eligible service, and keep the reservation until you deliberately release it or the service’s terms require otherwise.

Providers use different names and support different operations:

• DigitalOcean Reserved IPs are static public IPv4 and IPv6 addresses that can be assigned and reassigned to eligible Droplets. See DigitalOcean’s overview.
• AWS Elastic IP addresses are retained public IPv4 addresses, with reassignment restricted to the applicable AWS Region. See the Elastic IP guide.
• Google Cloud static external IP addresses can be reserved and assigned to compatible resources. See Google Cloud’s configuration guide.

These products illustrate the concept; their limits are not interchangeable. Check address-family support, regional scope, and resource compatibility for the service you use.

Why would you reserve an IP address?

Consider a small application with a public endpoint. Customers have added its address to their access rules, and a DNS record points to it.

If the application moves to a replacement server, retaining the endpoint can reduce the number of settings that need updating. Where supported, the reservation lets you associate the existing address with the replacement resource instead of obtaining a new address.

That only solves the addressing part of the move. The replacement still needs the application, data, routing, and security configuration required to serve traffic.

Other reasons to retain an address include preparing a service before its server exists or keeping a stable destination for a VPN gateway. For predictable outgoing traffic, first confirm that the product uses the reserved address as its source address.

Does a reserved IP control both incoming and outgoing traffic?

Not necessarily. Assigning an address to receive connections does not universally mean all outgoing traffic will use it.

For example, DigitalOcean publishes separate instructions for sending outbound traffic over a reserved IP. This matters when a partner approves the source address of your connections.

Check the address from the destination’s point of view, and follow the provider’s documented configuration. An inbound endpoint and an outbound source can be different addresses. What Is NAT? explains one reason this happens.

What is a DHCP reservation?

A DHCP reservation is a local network rule tying an address to a recognized device. The device keeps using DHCP to request its settings; the server supplies the reserved address when the rule matches.

For example, a network administrator might reserve 192.168.10.50 for an office printer. Microsoft’s DHCP server guide describes creating reservations using an IP address and the MAC address of the device’s network interface.

This does not reserve a public internet address or make the printer reachable from outside the office. Its scope is the network served by that DHCP configuration. Read Static vs Dynamic IP Addresses for a comparison with manual assignment.

What are special-purpose or reserved address ranges?

Networking standards designate some address ranges for specific functions. Examples include:

• 10.0.0.0/8 for private IPv4 networking.
• 127.0.0.0/8 for IPv4 loopback, including the familiar 127.0.0.1 address.
• 192.0.2.0/24 for documentation examples.

These categories appear in IANA’s IPv4 special-purpose registry. Each has its own rules; special-purpose does not mean that every range behaves like private address space.

A private range can be used by many unrelated networks. It is therefore different from an address a cloud provider holds for one account. Our public vs private IP guide explains that distinction.

Is a reserved IP the same as a static or dedicated IP?

A reserved cloud address is commonly static, but the words emphasize different properties. Reserved describes how an address is set aside. Static describes the stability of the assignment. Dedicated describes exclusive use within a service.

An offer may include all three properties, but read its actual terms. A reserved address may also be idle, with no service attached to it. Reservation and active use are separate states.

See Dedicated vs Shared IP Addresses for how exclusivity affects different workloads.

What should you check before relying on a reservation?

Confirm these details in the provider’s documentation:

• Whether the address survives deletion or replacement of the attached resource.
• Which resources, regions, and IP versions it supports.
• Whether incoming and outgoing traffic use the same address.
• Whether retaining an unused address incurs charges.
• What happens when you unassign, release, or cancel it.

For example, AWS documents charges for Elastic IPs whether attached or idle. Releasing an address is also different from detaching it: detachment may retain the reservation, while release returns the address to the provider’s available resources.

FAQ

Related resources