Networking: ordering an additional IP and configuring it

Your VPS ships with a primary IP, included in the plan. You can add more, for instance to host several sites with separate certificates, isolate a service or keep mail apart from the rest.

Where do I see the IP addresses of my VPS?

Open My services, your VPS, then the Network tab. For each address the table shows:

• IP address;
• MAC address, with a Copy MAC button;
• Type: Principale or Additionnelle;
• Monthly price: Incluse for the primary IP, the monthly rate for the others;
• Note: a free-text note such as public website or test server;
• Actions: deletion, available for additional IPs only.

The panel points out that the MAC is locked to the IP at the level of our address manager. That pairing is deliberate: it prevents a machine from claiming an address that is not its own. You therefore cannot change a MAC, and you do not need to.

How do I order an additional IP for my VPS?

From the Network tab, in the Additional IPs section: enter the quantity, click Order an IP, then pay the invoice that is generated. Four additional addresses per VPS at most.

1. In the Network tab, find the Additional IPs section. It shows how many addresses are in use out of the allowance, together with the monthly rate per IP.
2. Enter the Quantity you want.
3. Click Order an IP.
4. Pay the resulting invoice if one is issued. Depending on the configuration, the address is provisioned after payment.

The maximum is four additional IPs per VPS. Beyond that the panel shows "Limite maximale atteinte pour ce produit."

Once the address is allocated, a new network interface is added to your VPS automatically with the dedicated MAC. What remains is to configure the address inside the operating system.

How do I configure an additional IP in Linux?

With Netplan on Debian and Ubuntu, with nmcli on AlmaLinux, Rocky and CentOS Stream: the address goes on the new interface, with the same gateway and prefix as the main IP.

First find the name of the new interface and the settings of the primary one:

ip -br link          # the new interface appears, without an address
ip -4 addr
ip route

An additional IP normally uses the same gateway and the same prefix as your primary IP. If you have the slightest doubt, open a ticket with the technical team before changing your configuration.

Recent Debian and Ubuntu, with Netplan. Edit the file in /etc/netplan/:

network:
  version: 2
  ethernets:
    ens19:
      addresses:
        - ADDITIONAL_IP/PREFIX

Then apply carefully:

netplan try
netplan apply

netplan try reverts to the previous configuration on its own if the new one cuts your session — exactly what you want when changing networking remotely.

With NetworkManager, on AlmaLinux, Rocky Linux or CentOS Stream:

nmcli con add type ethernet ifname ens19 con-name ip2 \
  ip4 ADDITIONAL_IP/PREFIX
nmcli con up ip2

Then check:

ip -4 addr show ens19
ping -c3 -I ADDITIONAL_IP 9.9.9.9

How do I change the reverse DNS of my IP address?

Reverse DNS cannot be changed from the client area: the request goes through a ticket to the Service Technique.

Reverse DNS maps a name to your IP address. It is useful, and effectively mandatory, for a mail server. It cannot be set from the client area: open a ticket with the Service Technique, quoting the IP address concerned and the desired name, which must itself point to that IP.

How do I remove an additional IP?

Select the row and click Delete, or tick several addresses for a bulk removal. The confirmation lists the addresses concerned and states that the action is immediate. Remove the address from your system configuration and your DNS zones first: an IP still referenced in an A record would keep sending visitors nowhere.

The primary IP cannot be deleted; the panel says so explicitly.

My new IP does not work, what should I check?

Five checks, in order: the address actually set on the interface, the default route, a ping to the gateway then to a public IP, the number of interfaces the system sees, and firewall rules bound to a single interface.

1. ip -4 addr: is the address actually set on the interface?
2. ip route: does a default route exist?
3. ping the gateway, then a public IP, then a domain name — whichever step fails names the guilty layer.
4. Compare the number of interfaces the system sees with the number of addresses listed in the Network tab.
5. Check that your firewall is not applying a rule to a single interface.