Every DartNode virtual server comes with IPv6 alongside IPv4. When IPv6 isn't working, it's usually one of three things. The network configuration inside the server may be out of date, a firewall may be blocking IPv6 traffic, or, less often, there's a network-wide issue on our side. This guide walks through each one, in the order you should check them.

Step 1: Check whether it's just you

If several customers report IPv6 problems at the same time, it's almost certainly a network event, and we'll already be working on it. Check for an active incident or notice before you troubleshoot your own server. If there is one, you don't need to open a ticket. Your service is covered by the incident.

Step 2: Reconfigure the network from the dashboard

This fixes most single-server IPv6 problems, especially on servers that were reinstalled, restored from a snapshot, or had network settings changed by hand.

1. Open the server's page in the dashboard.
2. In the Networking section, click Reconfigure Network.
3. Wait a minute, then test again.

This pushes your assigned IPv4 and IPv6 addresses and gateways back to the server. It doesn't reboot the server or touch your data. More detail is in Fixing Connectivity Issues (Reconfigure Network).

Step 3: Confirm the server actually has its address

From the VNC console or SSH, run:

ip -6 addr show        # your 2602:… address should be listed as "scope global"
ip -6 route show       # there should be a "default via …" route
ping -6 -c 4 2606:4700:4700::1111

• No global IPv6 address: the configuration didn't apply. Run Reconfigure Network again and check that your OS's network config (netplan, /etc/network/interfaces, or NetworkManager) hasn't been edited to disable IPv6.
• Address present but no default route: the gateway is missing. Reconfigure Network should restore it.
• Address and route present, but ping fails: go to step 4.

Step 4: Check your firewall

Many firewall setups treat IPv4 and IPv6 separately, so it's easy to allow traffic on one and accidentally block it on the other.

• UFW: make sure IPV6=yes is set in /etc/default/ufw, then run ufw reload.
• iptables: rules in iptables don't apply to IPv6. Check ip6tables -L -n as well.
• ICMPv6: don't block it entirely. IPv6 depends on ICMPv6 for neighbor discovery, and blocking it breaks connectivity in ways that look like a routing problem.

Step 5: Inbound works but outbound doesn't, or the reverse

If you can reach the internet over IPv6 but nothing can reach your server (or the other way round), test from several external locations before assuming a fault. One remote network having an IPv6 routing problem is common and has nothing to do with your server. If it fails from everywhere, open a ticket.

When to open a ticket

If you've run Reconfigure Network and checked your firewall, and IPv6 still fails, open a ticket. Include:

• The service ID and its IPv6 address
• Output of ip -6 addr and ip -6 route
• A traceroute6 or mtr -6 to the destination that fails
• Whether the problem is inbound, outbound, or both

Open one ticket per issue. Duplicate tickets get merged and don't speed up the response.

Other IPv6 questions

My IPv6 address shows the wrong country in geolocation databases. Third-party databases (Google, MaxMind, and others) sometimes misplace new IPv6 ranges. Open a ticket and we can submit corrections. Updates are controlled by those providers and can take a few weeks.

Can I turn IPv6 off? Yes. You can disable it inside your operating system. Your server's IPv4 connectivity isn't affected.

Can I set reverse DNS for my IPv6 address? Yes. See How to Configure Reverse DNS.