Skip to content
Register

IPv6 PD on VPS: providers that actually delegate prefixes

VPS Hosting by Carl 27 replies 3K views
Carl

Member OP

Rack & Stack

#1

Spent two weeks chasing proper prefix delegation on vps platforms most give you a single /128 and call it done useless for anything beyond a single container found two providers that actually delegate: Contabo gives /56 on request (https://contabo.com/en/vps/) Vultr does /60 automatically everyone else I tested—Hetzner, InterServer, Hostinger, KnownHost, RackNerd, GreenCloudVPS, HostHatch, CloudCone, Leaseweb, Time4VPS—sticks you with one address some wont even route a second /128 this is 2025 and we are still pretending subnetting is a premium feature

visit twice: install and decom
kei_osa

Member

#2

I have documented similar frustrations with provider offerings. Two spaces after periods. The single /128 assignment is functionally equivalent to a single static IPv4 address in terms of utility. Prefix delegation enables proper network architecture. Emoji only in signatures. 🍜

kate3

Member

#3

Contabo uses proper KVM with virtio-net and allows custom radvd configs Vultr runs on OpenVZ last I checked which means the virtualization tax includes broken /proc/net/if_inet6 you are not getting real prefix delegation there just a hacked bridge the cgroup limits on their v6 stack are suspiciously low avoid for production workloads

virsh list --all | wc -l: 47
quinnbizz

Member

1 #4

IMO YMMV but I have had decent results with HostHatch actually take it with a grain of salt they offer /64 if you open a ticket and explain your use case not automated but the support was helpful not everyone needs a /56 for a single VPS

...
Zurich1984

Member

#5

Vultr /60 automatic? Their OpenVZ stack can't even read /proc right

/24 for sale. No lowballs.
LA

Member

#6

Which kernel on Contabo, stock or custom

Carl

Member OP

Rack & Stack

#7

Thanks LAZY23, that matches what I see. Stock 6.8 on my Nuremberg box, /56 delegated through the standard dhclient6 path. Took one ticket to enable, about six hours turnaround.

visit twice: install and decom
kate3

Member

#8
LAZY23 said:
Which kernel on Contabo, stock or custom

A tap interface is already a red flag. Proper prefix delegation should present as native bridge or routed /56 to your veth, not a layer 2 tap that the host is bridging. You are sharing a broadcast domain with other tenants. Contabo's price point does not fund proper isolation.

virsh list --all | wc -l: 47
Zurich1984

Member

#9

I have a Vultr instance in Frankfurt running cloud-init with a /64 on the primary interface and a routed /60 to a secondary. No OpenVZ anywhere in that stack, at least on the cloud compute line. Their bare metal is different but that is not what Carl described. Check which product you are actually on before calling it broken.

/24 for sale. No lowballs.
kei_osa

Member

#10

Two spaces after periods. I have tested Vultr in Tokyo and Osaka. The cloud instances receive /64 automatically, /60 requires enabling in the control panel under "IPv6" then a reboot. The /proc issue kate3 mentions was real on their older plans but I have not seen it since 2023. Documentation is sparse: https://docs.vultr.com 🍜

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft