How do I check IPv6 on a VPS?
IPv6 requires an assigned address or prefix, a valid route and appropriate service and firewall configuration. Publishing an AAAA record before that path works can send users to an unreachable endpoint. Use the provider’s actual allocation, not an invented address.
Instructions
1. Confirm the assigned IPv6 configuration
Review the selected VPS Networking details and ask for the prefix length, routing method and any required gateway or router-advertisement behaviour. IPv4 settings do not automatically establish IPv6 connectivity.
2. Inspect the Linux guest
Check current IPv6 state without changing it.
ip -6 address show
ip -6 route
sudo ss -lntpVerify the intended address is usable, a suitable route exists and the application listens on the required address family. Link-local addresses alone do not establish public IPv6 access.
3. Test from an IPv6-capable client
Use the actual assigned address in place of the documentation example.
Test-NetConnection -ComputerName '2001:db8::10' -Port 22This tests the chosen TCP service through the client’s IPv6 path. Confirm the client network actually has IPv6 connectivity.
Check the result
- The guest has the approved IPv6 address and route.
- The real service works externally over IPv6 before its public AAAA record is relied on.
Troubleshooting
- IPv4 works but IPv6 fails
- Review IPv6-specific routes, firewall rules and listener bindings separately.
- The provider has not allocated IPv6
- Ask about availability for the exact service rather than configuring an arbitrary public prefix.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.