IPv4 and IPv6 settings on a dedicated server
This guide shows how to set static IPv4 and IPv6 addresses on a dedicated server. Use it when you add an IPv6 subnet or additional IPv4 addresses, or when you need to restore the network settings of the server.
Before you start
All network parameters of your server are listed in the client area: Order Details, Network tab. You will need the IP address, netmask and gateway for IPv4, and the subnet and gateway for IPv6. Additional IP addresses appear as separate rows in the same table. For details, see the manual "Network information".

An IPv6 subnet is shown in the client area for DC1 servers. For servers in other data centers, IPv6 is issued on request. Create a ticket to the support team.
Linux uses a prefix length instead of a netmask. The most common values are 255.255.255.0 = /24, 255.255.255.248 = /29, 255.255.255.255 = /32. An additional IP address may have a different netmask than the main one: always take the netmask for each address from its own row in the Network tab. An additional address with the /32 netmask is added without a gateway of its own: traffic goes through the gateway of the main address.
On some servers the main IPv4 address is assigned via DHCP. If you switch such a server to a static configuration, enter exactly the address, netmask and gateway shown in the Network tab.
A mistake in the network settings cuts off SSH or RDP access to the server. Before you change anything, make sure you can reach the server through IP-KVM (the REQUEST button in Order Details). Apply the changes from the IP-KVM console if possible.
The examples below use documentation addresses. Replace them with the values from your Network tab:
- IPv4 address
203.0.113.10/24, gateway203.0.113.1 - additional IPv4 address
203.0.113.11/24 - IPv6 address
2001:db8:1234::2/64, gateway2001:db8:1234::1 - DNS servers
1.1.1.1,8.8.8.8,2606:4700:4700::1111
Find the network interface name
On Linux, run:
ip -br link
The interface with state UP and a name like eno1, enp1s0 or eth0 is the one you need. The examples below use eno1.
Ubuntu (netplan)
Ubuntu 22.04 and 24.04 keep network settings in YAML files in /etc/netplan/. List them:
ls /etc/netplan/
Make a backup of the file you found and open it for editing. The commands below use 50-cloud-init.yaml as an example: replace it with the name from your server.
cp /etc/netplan/50-cloud-init.yaml /root/50-cloud-init.yaml.bak nano /etc/netplan/50-cloud-init.yaml
Replace the contents with:
network: version: 2 ethernets: eno1: dhcp4: false dhcp6: false accept-ra: false addresses: - 203.0.113.10/24 - 203.0.113.11/24 - 2001:db8:1234::2/64 routes: - to: default via: 203.0.113.1 - to: default via: 2001:db8:1234::1 nameservers: addresses: [1.1.1.1, 8.8.8.8, 2606:4700:4700::1111]
Remove the line with 203.0.113.11/24 if you have no additional IP addresses. YAML is sensitive to indentation: use spaces, not tabs.
Set strict permissions on the file, then apply the configuration in test mode:
chmod 600 /etc/netplan/50-cloud-init.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.
If cloud-init manages the network configuration, it may overwrite 50-cloud-init.yaml after a reboot. If you are going to manage the network with Netplan manually from now on, disable the network part of cloud-init before rebooting: create /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the line network: {config: disabled}.
Debian (ifupdown)
Debian 12 and 13 keep network settings in /etc/network/interfaces. Make a backup and open the file:
cp /etc/network/interfaces /root/interfaces.bak nano /etc/network/interfaces
Edit the section of your interface:
auto eno1 iface eno1 inet static address 203.0.113.10/24 gateway 203.0.113.1 iface eno1 inet static address 203.0.113.11/24 iface eno1 inet6 static address 2001:db8:1234::2/64 gateway 2001:db8:1234::1 accept_ra 0
The second inet block adds the additional IPv4 address. Remove it if you do not need it.
On a standard Debian server, /etc/resolv.conf is edited manually. Set the DNS servers there:
nameserver 1.1.1.1 nameserver 8.8.8.8 nameserver 2606:4700:4700::1111
If resolvconf or systemd-resolved manages /etc/resolv.conf, the file may be generated automatically. In that case, configure DNS through the service that manages it. For resolvconf, you can add the line dns-nameservers 1.1.1.1 8.8.8.8 to the inet static block in /etc/network/interfaces.
Apply the settings from the IP-KVM console:
systemctl restart networking
AlmaLinux and Rocky Linux (NetworkManager)
AlmaLinux and Rocky Linux 9 and 10 manage the network with NetworkManager. Find the connection name:
nmcli connection show
The examples below use the connection name eno1. For each address, use the prefix length shown in its row in the Network tab. Set the IPv4 parameters:
nmcli connection modify eno1 ipv4.method manual ipv4.addresses "203.0.113.10/24,203.0.113.11/24" ipv4.gateway 203.0.113.1 ipv4.dns "1.1.1.1 8.8.8.8"
Set the IPv6 parameters:
nmcli connection modify eno1 ipv6.method manual ipv6.addresses 2001:db8:1234::2/64 ipv6.gateway 2001:db8:1234::1 ipv6.dns 2606:4700:4700::1111
Apply the changes:
nmcli connection up eno1
To add one more IPv4 address later without retyping the list, use the plus sign:
nmcli connection modify eno1 +ipv4.addresses 203.0.113.12/24 nmcli connection up eno1
Windows Server
The steps are the same for Windows Server 2022 and 2025.
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. Below, enter the DNS servers.

To add an additional IPv4 address, click Advanced, then Add in the IP addresses section. Enter the address and subnet mask. Do not add a second gateway.

Return to the adapter properties, select Internet Protocol Version 6 (TCP/IPv6) and click Properties. Enter the IPv6 address, the subnet prefix length (for example, 64), the default gateway and the DNS server.

Click OK in all windows to apply the settings.
PowerShell
Open PowerShell as administrator and find the adapter name:
Get-NetAdapter
The examples below use the name Ethernet. If the adapter already has a static address that you want to replace, remove it first with Remove-NetIPAddress, otherwise New-NetIPAddress returns an error. If the adapter currently gets its address via DHCP, disable it first:
Set-NetIPInterface -InterfaceAlias "Ethernet" -Dhcp Disabled
Set the main IPv4 address and gateway:
New-NetIPAddress -InterfaceAlias "Ethernet" -IPAddress 203.0.113.10 -PrefixLength 24 -DefaultGateway 203.0.113.1
Add an additional IPv4 address (without a gateway):
New-NetIPAddress -InterfaceAlias "Ethernet" -IPAddress 203.0.113.11 -PrefixLength 24
Set the IPv6 address and gateway:
New-NetIPAddress -InterfaceAlias "Ethernet" -AddressFamily IPv6 -IPAddress 2001:db8:1234::2 -PrefixLength 64 -DefaultGateway 2001:db8:1234::1
Set the DNS servers:
Set-DnsClientServerAddress -InterfaceAlias "Ethernet" -ServerAddresses ("1.1.1.1","8.8.8.8","2606:4700:4700::1111")
Check the settings
On Linux, check the addresses and routes:
ip addr show eno1 ip route ip -6 route
Check the connection over IPv4 and IPv6:
ping -c 4 1.1.1.1 ping -6 -c 4 2606:4700:4700::1111
Check that DNS resolves names:
getent hosts introserv.com
On Windows Server, run:
ipconfig /all ping 1.1.1.1 ping -6 2606:4700:4700::1111 Resolve-DnsName introserv.com
If the IPv4 ping works and the IPv6 ping fails, check the IPv6 gateway and the prefix length against the Network tab. If the problem persists, see the manual "Network Connectivity Troubleshooting" or contact support.