> ## Documentation Index
> Fetch the complete documentation index at: https://gcore-doc-1046.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Create and configure a reserved IP address
A reserved IP is a dedicated address that can be assigned to a [Virtual Machine](/cloud/virtual-instances/create-an-instance), [Bare Metal server](/cloud/bare-metal-servers/create-a-bare-metal-server), or [Load Balancer](/cloud/networking/create-and-configure-a-load-balancer). It exists independently of resources, can be pre-configured in DNS or firewall rules, and remains valid when reassigned. A reserved IP can also be used as a [Virtual IP address](/cloud/networking/ip-address/create-and-configure-a-virtual-ip-vip-address).
## Overview
After a reserved IP is created, this address is exclusively allocated within the Gcore system. No other account can use it. The IP can be assigned to a resource or kept unassigned for future use. An existing port attached to a [Virtual Machine](/cloud/virtual-instances/create-an-instance) or [Load Balancer](/cloud/networking/create-and-configure-a-load-balancer) can also be marked as reserved to protect it from deletion.
## Billing
The monthly price for the IP is displayed in the order window. Billing applies only for the time from creating an IP to deleting it.
If an IP is reserved and deleted after an hour, charges apply only for that hour. The price remains the same whether the IP is assigned or not.
## Reserve an IP address
To create a new reserved IP:
1. In the [Gcore Customer Portal](https://portal.gcore.com/accounts/reports/dashboard), navigate to **Cloud** > **Networking**.
2. Open the **Reserved IPs** page.
A project can have up to 1000 reserved fixed IP addresses that are not attached to any resource.
3. Click **Reserve new IP**.
4. In the **Network** field, select the network type:
* **Public**: External network for internet-facing IP addresses.
* **Private**: Internal network within the project. For this option, select the [network](/cloud/networking/create-and-manage-a-network) and optionally a specific [subnetwork](/cloud/networking/create-and-manage-a-subnetwork).
* **Dedicated public**: Dedicated public network (if configured for the project).
When a network is selected without specifying a subnetwork, the IP address is allocated in any available subnet of that network.
A reserved private IP works within the specified subnetwork. To request a specific address, in the **IP address to reserve** section, select **Custom** and enter the IP that belongs to that subnetwork.
5. (Optional) In the **IP Family** section, select the IP version: **IPv4**, **IPv6**, or **Dual (IPv4 + IPv6)**.
6. Click **Reserve IP**.
## Assign a reserved IP to a VM
Refer to the [VM creation](/cloud/virtual-instances/create-an-instance#step-5-add-network-interfaces) guide.
1. In the Virtual Machine settings, open the **Networking** tab.
If the machine is already connected to the target subnetwork, detach it first before assigning a new IP. This removes the existing IP from the interface.
2. Add a new interface (public or private) and enable the **Use reserved IP** toggle.
3. Select the reserved IP and click **Add**.
The IP will be assigned to the Virtual Machine.
## Configure the network interface in the operating system
Manual configuration is required only when adding a private interface to an existing VM or Bare Metal server.
Find the interface name, IP address, and CIDR in the **Networking** tab. The gateway is the first usable IP in the subnet (`10.10.0.1` for `10.10.0.0/24`).
To identify the new interface, run `ip link show` and match the MAC address shown in the portal.
If the network has DHCP enabled, request an IP address automatically:
```sh theme={null}
sudo dhcpcd
```
Example:
```sh theme={null}
sudo dhcpcd enp4s0
```
This configuration is lost after a reboot.
Assign a static IP address manually:
```sh theme={null}
sudo ip link set up
sudo ip addr add / dev
sudo ip route add via dev
```
Example:
```sh theme={null}
sudo ip link set enp4s0 up
sudo ip addr add 172.18.220.100/22 dev enp4s0
```
This configuration is lost after a reboot.
For Ubuntu 24.04 and other Netplan-based distributions, create a configuration file:
```sh theme={null}
sudo bash -c 'cat < /etc/netplan/51-new-interface.yaml
network:
version: 2
ethernets:
enp4s0:
dhcp4: true
EOF'
```
Apply the configuration:
```sh theme={null}
sudo netplan apply
```
For Ubuntu 24.04 and other Netplan-based distributions, create a configuration file:
```sh theme={null}
sudo bash -c 'cat < /etc/netplan/51-new-interface.yaml
network:
version: 2
ethernets:
enp4s0:
dhcp4: false
addresses:
- 192.168.1.10/24
gateway4: 192.168.1.1
nameservers:
addresses:
- 95.85.95.85
- 2.56.220.2
EOF'
```
Replace `enp4s0`, IP address, gateway, and nameservers with the actual values.
Apply the configuration:
```sh theme={null}
sudo netplan apply
```
1\. Open **Control Panel** > **Network and Sharing Center** > **Change adapter settings**.
2\. Right-click the new network adapter and select **Properties**.
3\. Select **Internet Protocol Version 4 (TCP/IPv4)** and click **Properties**.
4\. Select **Use the following IP address** and enter the IP address, subnet mask, and default gateway.
5\. Click **OK** to save the settings.
The [Virtual IP (VIP) address configuration](/cloud/networking/ip-address/create-and-configure-a-virtual-ip-vip-address#configure-a-virtual-ip-address-for-non-windows-virtual-machines) guide contains additional configuration examples.
## Detach a reserved IP from a VM
Detaching is required before reassigning the IP to another resource or deleting it.
1. Open the Virtual Machine settings.
2. Go to the **Networking** tab.
3. Expand the interface that contains the reserved IP.
4. Click the three-dot menu next to the subnetwork row.
5. Select **Detach Subnetwork**.
## Assign a reserved IP to a load balancer
Reserved IP assignment is available during Load Balancer creation.
The IP becomes the frontend address and is tightly bound to the frontend network interface. It cannot be changed after provisioning.
For instructions, refer to the [Load Balancer creation](/cloud/networking/create-and-configure-a-load-balancer#step-4-configure-network) guide.
## Find a resource with reserved IP
The **Status** column on the **Reserved IPs** page shows if an IP is attached to a resource:
Click the resource name to view and update its settings.
## Delete a reserved IP
After verifying that the IP is no longer attached to any resource, it can be deleted:
1. In the [Gcore Customer Portal](https://portal.gcore.com/accounts/reports/dashboard), navigate to **Cloud** > **Networking**.
2. Open the **Reserved IPs** page.
3. Click the three-dot icon next to the target IP.
4. Select **Delete**.
