Dedicated Server IP Migration Guide

As part of the upcoming IP migration, your dedicated server has been assigned new network information.

Dedicated servers may have:

• A primary IP range assigned to the server.
• One or more additional routed IP blocks

To ensure network connectivity after the migration, you'll need to update your server's network configuration using the new IP information provided by CloudCone before the deadline on September 01ˢᵗ 2026.

Before You Begin

Your new network information is available in your Dedicated Server management page in app.cloudcone.com.

The following information will be displayed:

Before making any changes, make sure you have noted the new values for your server.

Ubuntu & Debian

Method 1 - Netplan (Ubuntu 18.04+)

1. Locate your Netplan configuration

ls /etc/netplan/

2. Edit the configuration

sudo nano /etc/netplan/<filename>.yaml

3. Update the network configuration

Replace your existing configuration with the new values.

Update:

• IP Address (using an address from your NEW IP BLOCK)
• Prefix/Netmask
• Gateway
• DNS (if required)

Example:

network:
  version: 2
  ethernets:
    eth0:
      dhcp4: false
      addresses:
        - NEW_IP/PREFIX
      routes:
        - to: default
          via: NEW_GATEWAY
      nameservers:
        addresses:
          - 1.1.1.1
          - 8.8.8.8

If your server has additional IP addresses configured directly on the interface, update those as well.

4. Apply the changes

sudo netplan apply

Method 2 - /etc/network/interfaces

1. Edit the configuration

sudo nano /etc/network/interfaces

2. Replace the existing values

Update:

• Address
• Netmask / Prefix
• Gateway

If additional IP addresses are configured as aliases or secondary addresses, update those as well.

3. Restart networking

sudo systemctl restart networking

or

sudo ifdown eth0 && sudo ifup eth0

CentOS / RHEL / Rocky / AlmaLinux

Method 1 - NetworkManager (Recommended)

1. List your connections

nmcli connection show

Locate the connection associated with your network interface.

2. Update the IP address

sudo nmcli connection modify "<connection-name>" ipv4.addresses NEW_IP/PREFIX

3. Update the gateway

sudo nmcli connection modify "<connection-name>" ipv4.gateway NEW_GATEWAY

4. Update DNS (if required)

sudo nmcli connection modify "<connection-name>" ipv4.dns "1.1.1.1 8.8.8.8"

5. Ensure the interface uses a static configuration

sudo nmcli connection modify "<connection-name>" ipv4.method manual

6. Apply the changes

sudo nmcli connection down "<connection-name>"
sudo nmcli connection up "<connection-name>"

Method 2 - Legacy Network Scripts

1. Edit the interface configuration

sudo nano /etc/sysconfig/network-scripts/ifcfg-<interface>

The interface may be named:

• eth0
• ens3
• ens160
• eno1
• or another name depending on your hardware.

2. Update the following values

• IPADDR
• PREFIX (or NETMASK)
• GATEWAY
• DNS1
• DNS2 (if required)

3. Save the file.

4. Restart networking

sudo systemctl restart NetworkManager

or

sudo systemctl restart network

Additional Routed IP Blocks

Many dedicated servers have one or more additional IP blocks assigned.

The most common configuration is a /29, although some servers may have multiple /29 blocks or larger routed subnets.

If your server uses these additional IPs for:

• Websites
• Virtual Machines
• Containers
• Reverse Proxies
• NAT
• Firewall Rules
• Other Services

you will also need to update those configurations to use the new IP block(s).

Depending on your setup, these may be configured as:

• Secondary IP addresses
• Interface aliases
• Bridge interfaces
• Virtualization platform networking
• Custom network scripts

Please ensure any configuration referencing the old IP addresses is updated.

Verify the Configuration

Verify the assigned addresses:

ip addr

Verify the default route:

ip route

Test network connectivity:

ping -c 4 1.1.1.1

Verify DNS resolution:

ping -c 4 google.com

Don't Forget

After updating your server's IP configuration, you may also need to update:

• DNS records (A/AAAA records)
• Reverse DNS (rDNS)
• Firewall rules
• NAT rules
• Web server bindings
• Virtualization networking
• Any third-party allowlists or firewall rules referencing your old IP addresses

Failure to update these may result in connectivity issues even after your server is using the new IP addresses.

Need Assistance?

If you're unsure how your server is configured or need assistance updating your IP configuration, please open a support ticket before making any changes.

Our support team will be happy to assist you throughout the migration.

Updated on: 08/07/2026