Vultr DocsLatest Content

How to Configure Multiple Public IPv4 Addresses on a Vultr Compute Instance

Updated on 06 November, 2025
Guide
Learn how to assign and configure multiple public IPv4 addresses on Vultr Compute Instances for Ubuntu, CentOS, FreeBSD, and Windows.
How to Configure Multiple Public IPv4 Addresses on a Vultr Compute Instance header image

Assigning multiple public IP addresses to a Vultr Compute Instance allows you to host multiple services, bind applications to separate IPs, or configure advanced networking setups such as NAT or IP-based virtual hosts. Vultr makes it easy to add and manage additional IP addresses through the Vultr Customer Portal.

This guide explains how to assign and configure multiple public IPv4 addresses on a Vultr Compute Instance. It covers adding IPs from the portal, configuring the operating system, and verifying network connectivity.

Prerequisites

Before you begin, you need to:

Configure Multiple IPv4 Addresses on Ubuntu

Follow these steps to assign and configure multiple public IPv4 addresses on your Ubuntu instance.

  1. Log in to the Vultr Customer Portal.

  2. Navigate to Compute under the Products section.

  3. Select your Ubuntu server and click Settings.

  4. Under the IPv4 section, you can see the default IP address assigned to the server.

  5. Click Add Another IPv4 Address, check the box labeled Yes, add and restart this server, and click Add IPv4 Address to assign a new IPv4 address to your server.

  6. After the IP is assigned, you must manually configure it on the server.

  7. Click Network Configuration to generate and copy the custom Netplan template based on your OS.

  8. Below is an example configuration for Ubuntu server using Netplan.

    yaml
    network:
      version: 2
      renderer: networkd
      ethernets:
        enp1s0:
          dhcp4: no
          addresses: [192.0.0.4/23,192.0.2.5/32]
          nameservers:
            addresses: [192.0.0.6]
          routes:
          - to: default
            via: 192.0.0.1
          - to: 169.254.0.0/16
            via: 192.0.0.1
            metric: 100
    

    Replace the following values with those provided in your Vultr Customer Portal:

    • 192.0.2.5: Your newly assigned IPv4 address.
    • 192.0.0.6: Your DNS server.
    • 192.0.0.1: Your gateway IP.

    In the above configuration:

    • network: The top-level key that begins the Netplan configuration
    • version: Specifies the Netplan format version. Version 2 is the standard used in most modern Ubuntu systems.
    • renderer: Indicates which backend to use for applying the configuration.
    • ethernets: Defines Ethernet interface configurations. All Ethernet-based interfaces should be declared under this section.
    • enp1s0: The name of the network interface being configured.
    • dhcp4: no: Disables DHCP for IPv4, so the interface uses a static IP configuration.
    • addresses: A list of static IP addresses assigned to the interface.
    • nameservers: Specifies DNS resolver addresses.
    • routes: Adds static routes to control traffic flow.
    • to: default / via: 192.0.0.1: Sets the default gateway to 192.0.0.1, used for routing external traffic.
    • to: 169.254.0.0/16 / via: 192.0.0.1 / metric: 100: Routes link-local addresses via the same gateway with a metric of 100.
  9. After you have copied the configuration, SSH into your Ubuntu server.

  10. Create a new Netplan configuration file using a text editor such as nano.

    console
    $ sudo nano /etc/netplan/10-enp1s0.yaml
    
  11. Paste the copied configuration into the file, then save and exit.

  12. Set restrictive file permissions to prevent unauthorized changes.

    console
    $ sudo chmod 400 /etc/netplan/10-enp1s0.yaml
    
  13. Test the configuration before applying it permanently.

    console
    $ sudo netplan try
    

    This command applies the new network configuration temporarily and gives you 120 seconds to confirm that everything is working as expected. If the system loses connectivity or something goes wrong, Netplan automatically rolls back to the previous configuration after the timeout, preventing accidental lockouts on remote systems.

    • Press <kbd class="key">Enter</kbd> to accept and apply the changes permanently.
    • Press <kbd class="key">Esc</kbd> or wait for the timer to expire if something breaks.
  14. If everything works as expected, apply the configuration permanently.

    console
    $ sudo netplan apply
    
  15. Restart the server from the Vultr Customer Portal by clicking the Server Restart icon to make the changes take effect.

Conclusion

In this guide, you learned how to assign and configure multiple public IPv4 addresses to a Vultr Cloud Compute Instance across various operating systems, including Ubuntu, CentOS, FreeBSD, and Windows. You added additional IP addresses through the Vultr Customer Portal and configured each system to recognize the new IPs using platform-specific tools like Netplan, rc.conf, and the Windows Network Settings panel.

Comments