Getting IPv6 running
IPv6 works everywhere on our network. Every server gets an address, more are available on request, and there is no surcharge for using it.
Configuring the address
You get the address, the prefix length and the gateway. Add them to the interface the way your distribution expects, alongside your IPv4 configuration rather than instead of it — dual stack is the point.
Do not rely on router advertisements to configure a server. Static is predictable, survives reboots and does not change under you.
Checking it
ip -6 addr— is the address actually on the interface?ip -6 route— is there a default route via the gateway?ping6 2606:4700:4700::1111— does anything answer?curl -6 https://ifconfig.co— what does the outside see?
If the first two look right and nothing answers, tell us and we look at the port.
If your firewall is involved, remember that IPv6 rules are separate:
ip6tables and nftables treat the two families differently,
and a server that is closed on IPv4 can be wide open on IPv6.
Services, not just the kernel
Getting the interface up is half of it. Web servers, databases and mail daemons
often listen on IPv4 only until told otherwise. Check with
ss -ltnp what is actually bound to an IPv6 socket, and publish AAAA
records only once you have.
More addresses
Ask. There is no shortage and no charge, and a block makes life easier if you are running containers or many virtual hosts.
Still stuck? Mail support@novogara.com — an engineer answers, at any hour. Back to the knowledge base