IPv4 and IPv6 settings on a VPS
Every INTROSERV VPS gets an IPv4 address and an IPv6 address when it is created. The VPS receives its network settings automatically via DHCP, so in most cases you do not need to configure anything. This guide shows how to check the settings, how to add an additional IP address if it did not appear on its own, and which changes break the network.
Where to find your IP addresses
The IPv4 addresses of your VPS are shown in the client area: Orders → Order Details → Network tab, together with the netmask and gateway. The IPv6 subnet is listed on the Details tab, in Order parameters (IPv6: /112 Network). To see the IPv6 address itself, check it on the VPS as described in "Check the network settings". For details about the client area, see the manual "VPS Control Panel".
How the network works on a VPS
- IPv4 and IPv6 addresses, the gateway and DNS servers are obtained via DHCP.
- IPv4 addresses usually have a
/24mask (255.255.255.0), and the gateway is usually the.1address of the subnet. The IPv6 address is configured with a/112prefix. - The default DNS servers are
8.8.8.8and1.1.1.1. - Each IP address is bound to the MAC address of the VPS network adapter. Traffic from any other address or MAC is blocked.
Do not change the IP address, mask, gateway or MAC address of the VPS. If the network settings differ from the ones issued by DHCP, the VPS loses network access. If you configure the network statically, use exactly the values assigned to the VPS. If the network stops working after a change, open the Virtual Console in the VPS control panel and restore the previous configuration.
Check the network settings
Linux:
ip -br addr ip route ip -6 route
The output shows the interface name (for example, eth0 or ens3), the IPv4 and IPv6 addresses and the default routes. The examples below use the interface name eth0.
Check the connection over IPv4 and IPv6:
ping -c 4 1.1.1.1 ping -6 -c 4 2606:4700:4700::1111
Windows Server (Command Prompt or PowerShell):
ipconfig /all ping 1.1.1.1 ping -6 2606:4700:4700::1111
Additional IP addresses
When you order an additional IP address, it is usually added to the network interface of the VPS automatically, as a second address (alias). Run ip -br addr on Linux or ipconfig /all on Windows. If the new address is in the list, nothing else is needed.
If the address is not there, add it manually as described below. Keep DHCP for the main address and add only the additional one. The examples use the documentation address 203.0.113.11/24. Replace it with your additional IP address.
Open the Virtual Console in the VPS control panel before you start. If you make a mistake, you can fix the configuration from there.
Ubuntu (netplan)
Ubuntu keeps network settings in YAML files in /etc/netplan/. Do not edit the existing file: it may be regenerated when the VPS restarts. Create a separate file for the additional address instead.
Check the interface name used in the existing file:
cat /etc/netplan/*.yaml
Create a new file:
nano /etc/netplan/60-additional-ip.yaml
Add the following, with the same interface name as in the existing file:
network: version: 2 ethernets: eth0: addresses: - 203.0.113.11/24
YAML is sensitive to indentation: use spaces, not tabs. Netplan merges this file with the main one, so DHCP for the main address stays as it is.
Set strict permissions on the file and apply the configuration in test mode:
chmod 600 /etc/netplan/60-additional-ip.yaml netplan try
If the connection still works, press Enter to keep the settings. If you lose access, netplan rolls back the changes after 120 seconds.
Debian (ifupdown)
Debian with ifupdown keeps network settings in /etc/network/interfaces. If your VPS has YAML files in /etc/netplan/ instead, follow the Ubuntu (netplan) section. Check that this file includes the configuration files from /etc/network/interfaces.d/:
grep source /etc/network/interfaces
The output should contain the line source /etc/network/interfaces.d/*. If it is missing, add it to the end of /etc/network/interfaces.
Create a separate file for the additional address:
nano /etc/network/interfaces.d/60-additional-ip
Add:
iface eth0 inet static address 203.0.113.11/24
Do not add a gateway here: the main address already has one.
Add the address to the running system without restarting the network:
ip addr add 203.0.113.11/24 dev eth0
The file keeps the address after a reboot.
AlmaLinux and Rocky Linux (NetworkManager)
Find the connection name:
nmcli connection show
Add the additional address to the connection. Replace System eth0 with your connection name:
nmcli connection modify "System eth0" +ipv4.addresses 203.0.113.11/24
Find the device name of the interface:
nmcli device status
Apply the change to the interface without reconnecting it. Replace eth0 with the device name from the previous command:
nmcli device reapply eth0
The main address still comes from DHCP, NetworkManager adds the additional one next to it. The address stays after a reboot.
Windows Server
To add an additional IPv4 address on Windows Server, the adapter must first use a static IPv4 configuration: the Advanced settings for additional addresses are available only with a static address. Set the main address statically with exactly the same values that DHCP issued, then add the additional address.
The connection drops for a moment when you switch the adapter from DHCP to static. Make these changes from the Virtual Console, not over RDP.
First, write down the current values:
ipconfig /all
You need the IPv4 Address, Subnet Mask, Default Gateway and DNS Servers of the active adapter.
Graphical interface
Press Win + R, enter ncpa.cpl and press Enter. Right-click the network adapter and select Properties.
Select Internet Protocol Version 4 (TCP/IPv4) and click Properties. Select Use the following IP address and enter the IP address, subnet mask and default gateway from the ipconfig output. Below, enter the DNS servers.
Click Advanced, then Add in the IP addresses section. Enter the additional address and the subnet mask 255.255.255.0. Do not add a second gateway.
Click OK in all windows. Leave the IPv6 settings unchanged.
PowerShell
Open PowerShell as administrator and find the adapter name:
Get-NetAdapter
The examples below use the name Ethernet and the documentation addresses 203.0.113.10 (main), 203.0.113.11 (additional) and 203.0.113.1 (gateway). Use the values from ipconfig instead.
Switch IPv4 from DHCP to static. IPv6 keeps working via DHCP:
Set-NetIPInterface -InterfaceAlias "Ethernet" -AddressFamily IPv4 -Dhcp Disabled
Set the main address and gateway:
New-NetIPAddress -InterfaceAlias "Ethernet" -IPAddress 203.0.113.10 -PrefixLength 24 -DefaultGateway 203.0.113.1
Add the additional address without a gateway:
New-NetIPAddress -InterfaceAlias "Ethernet" -IPAddress 203.0.113.11 -PrefixLength 24
Set the DNS servers. Do not skip this step: after the switch to static, the DNS server list is empty:
Set-DnsClientServerAddress -InterfaceAlias "Ethernet" -ServerAddresses ("8.8.8.8","1.1.1.1")
Check the result
Run the commands from "Check the network settings" again. The additional address should be in the list, and both pings should work.
To make sure the address is reachable from outside, ping it from your own computer:
ping 203.0.113.11
If there is no reply, check that the firewall on the VPS allows ICMP. You can also check a service that listens on the additional address, for example a website or SSH.
If the VPS lost network access, open the Virtual Console and remove the change you made. If the problem persists, contact support.
