How to Configure Multiple Public IPv4 Addresses on a Vultr Compute Instance
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 Console.
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:
- Have access to Vultr Console.
Follow these steps to assign and configure multiple public IPv4 addresses on your Ubuntu instance.
Log in to the Vultr Console.
Navigate to Compute under the Products section.
Select your Ubuntu server and click Settings.
Under the IPv4 section, you can see the default IP address assigned to the server.
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.
After the IP is assigned, you must manually configure it on the server.
Click Network Configuration to generate and copy the custom Netplan template based on your OS.
Below is an example configuration for Ubuntu server using Netplan.
YAMLReplace the following values with those provided in your Vultr Console:
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 configurationversion: 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.
After you have copied the configuration, SSH into your Ubuntu server.
Create a new Netplan configuration file using a text editor such as
nano.CONSOLEPaste the copied configuration into the file, then save and exit.
Set restrictive file permissions to prevent unauthorized changes.
CONSOLETest the configuration before applying it permanently.
CONSOLEThis command applies the new network configuration temporarily and gives you
120seconds 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 Enter to accept and apply the changes permanently.
- Press Esc or wait for the timer to expire if something breaks.
If everything works as expected, apply the configuration permanently.
CONSOLERestart the server from the Vultr Console 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 Console and configured each system to recognize the new IPs using platform-specific tools like Netplan, rc.conf, and the Windows Network Settings panel.
Tags:Vultr Compute
0 Comments
Be the first to comment and share your perspective with the community.