Configuring a Secondary (Additional) IPv4 Address

Once you have ordered an additional IPv4 address in the MyTilaa dashboard, it is routed to your server. However, your Operating System does not know about this new address yet. You must manually configure it.

Scenario 1: Linux (Manual Configuration)

By default, Tilaa servers use Cloud-init (DHCP) to configure the network. To add a static secondary IP, we must first disable Cloud-init's network management, otherwise, it will overwrite your changes on the next reboot.

Step 1: Disable Cloud-init Network Config

Create a configuration file to tell Cloud-init to stop managing the network:

nano /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg

Paste the following content:

network: {config: disabled}

Step 2A: Configuration for Ubuntu / Debian (Netplan)

1. Open your Netplan configuration file (usually in /etc/netplan/, e.g., 50-cloud-init.yaml).

2. Modify the file to include both IP addresses under the existing interface (usually ens3 or eth0). Do not create a second interface block unless you actually have a second network card.

network:
    version: 2
    ethernets:
        ens3:
            dhcp4: no
            addresses:
                - 192.168.1.10/24  # Primary IP
                - 192.168.1.11/24  # Secondary IP (New)
            gateway4: 192.168.1.1  # Primary Gateway
            nameservers:
                addresses: [1.1.1.1, 8.8.8.8]

3. Apply the changes:

netplan apply

Step 2B: Configuration for AlmaLinux / Rocky / CentOS

1. Open the network script for your interface (e.g., eth0):

nano /etc/sysconfig/network-scripts/ifcfg-eth0

2. Change BOOTPROTO to static and add the secondary IP details using the alias syntax (IPADDR1, IPADDR2, etc).

BOOTPROTO=static
DEVICE=eth0
ONBOOT=yes
TYPE=Ethernet

# Primary IP
IPADDR=192.168.1.10
PREFIX=24
GATEWAY=192.168.1.1

# Secondary IP
IPADDR1=192.168.1.11
PREFIX1=24

DNS1=1.1.1.1

3. Restart the network:

systemctl restart network
# OR
nmcli networking off && nmcli networking on

Scenario 2: Control Panels (cPanel / DirectAdmin)

If you are running a hosting panel, do not edit the Linux network files manually. The panel manages this for you.

• DirectAdmin: Log in as Admin > IP Management > Add IP.
• cPanel / WHM: Log in to WHM > IP Functions > Add a New IP Address.

Scenario 3: Windows Server

1. Log in via Remote Desktop (RDP).
2. Open Network Connections (ncpa.cpl).
3. Right-click your Ethernet adapter > Properties.
4. Select TCP/IPv4 > Properties.
5. Ensure your Primary IP is set statically (not DHCP).
6. Click the Advanced button.
7. Under the "IP addresses" section, click Add and enter your new Secondary IP and Subnet Mask.