How to configure IPv6 on VPS

Quick answer: Take the IPv6 address/subnet and gateway from your Client Area service page, add them to the OS network config — netplan on Ubuntu, /etc/network/interfaces on Debian, nmcli on AlmaLinux/Rocky — apply, then verify with ping -6 google.com. Don't forget firewall rules for the v6 stack.

Overview

Most images ship with IPv4 preconfigured; IPv6 sometimes needs adding by hand. The values are exactly analogous to v4: an address with prefix length (usually /64) and a gateway. Replace the 2001:db8:… examples below with the real values from your Client Area.

Before you start

• Your IPv6 address/prefix and gateway from the service page (or support).
• Root SSH access; know which interface you're editing (ip link — often eth0 or ens3).
• A KVM console fallback in the Client Area in case networking breaks.

Step-by-step guide

1. Ubuntu (netplan):

   sudo nano /etc/netplan/50-cloud-init.yaml

   network:
     version: 2
     ethernets:
       eth0:
         addresses:
           - "2001:db8:1234::2/64"
         routes:
           - to: "::/0"
             via: "2001:db8:1234::1"

   sudo netplan try   # auto-reverts in 120s if you lose the session
   sudo netplan apply

2. Debian (ifupdown): append to /etc/network/interfaces:

   iface eth0 inet6 static
       address 2001:db8:1234::2
       netmask 64
       gateway 2001:db8:1234::1

   sudo systemctl restart networking

3. AlmaLinux / Rocky (NetworkManager):

   sudo nmcli con mod "System eth0" ipv6.method manual \
     ipv6.addresses 2001:db8:1234::2/64 ipv6.gateway 2001:db8:1234::1
   sudo nmcli con up "System eth0"

4. Verify:

   ip -6 addr show eth0
   ping -6 -c 4 2001:4860:4860::8888   # Google DNS
   ping -6 -c 4 google.com

5. Firewall + DNS: mirror your rules for v6 (ufw does both if enabled; raw iptables needs ip6tables), then publish an AAAA record once stable.

Common issues

• Address pings locally but not the Internet: missing/typo'd gateway or default route — check ip -6 route.
• Works after apply, dead after reboot: config edited in the wrong file (cloud-init may regenerate netplan — use a separate file like /etc/netplan/60-ipv6.yaml).
• Locked out after firewall change: use the KVM Console from the Client Area to fix rules.

When to contact support

If the assigned prefix/gateway don't work despite correct config, send your ip -6 addr, ip -6 route and ping outputs — we'll check the network side.

Frequently asked questions

Where do I find my IPv6 address and gateway?

On the service page in the Client Area; if it is not listed, ask support whether IPv6 is available for your service and location.

How do I test that IPv6 works?

Run ip -6 addr, then ping -6 2001:4860:4860::8888 and ping -6 google.com. If local pings work but Internet does not, check the gateway/default route.

When should I publish the AAAA record?

Only after IPv6 is configured and tested — a premature AAAA record sends v6-capable visitors to a dead address.

Related articles

• IPv4 and IPv6 overview
• How to request additional IPv4 for VPS
• How to check traceroute / MTR
• How to report network issues to support

Need a hand? Contact Cloud2Y support →