Your server can have both a public IPv4 address and an IPv6 allocation. The assigned addresses identify the service and its network; they are separate from its hostname and billing Service ID.
Reviewed: 15 November 2026. Screenshots show the actual panel with server identifiers and addresses removed. Networking options depend on your service and permissions.
Find the assigned addresses
In the customer portal, open Services or your dashboard. Active service cards show live IP addresses when the panel can be reached; use the copy button beside the desired address. Select the service and compare its full Service ID before opening Open full VPS control panel through the acknowledgement.
In the full panel, the server header shows the primary address; an additional-address indicator may reveal more. The inspected Networking tab includes Manage IPv6 Subnets and VPC Network. A VPC is private networking where available; do not treat it as an automatically configured public IPv6 connection.
Select a screenshot to open it at full size.
Understand an IPv6 subnet
An address such as 2001:db8:1234:5678::1/64 contains both a host address and a prefix length. /64 describes the subnet size, not part of a single bare IP address. The 2001:db8::/32 range used here is reserved for documentation and must not be configured as your public allocation.
When a program asks for an IP address, it commonly needs only the address portion; a network configuration may also require the prefix. Use your actual assigned prefix, gateway and routing instructions. Do not infer the gateway from ::1, copy a neighbour's address or use a subnet merely because it appears in an example.
Manage only the allocation belonging to this VPS
Open Networking → Manage IPv6 Subnets and identify the correct row. If editing is available, its pencil control opens the subnet's permitted management options. Review the fields and current values before saving anything. The fields can vary by panel release and administrator policy; this guide does not assume a particular number of usable addresses or auto-configuration behavior.
Before applying a network change, save the current guest configuration and confirm that the VNC console works. Keep a recovery route. A wrong prefix, gateway or firewall rule can disconnect SSH even if the panel still shows the VPS as online. Schedule changes that may restart networking or the server.
A panel allocation alone does not prove that the address is configured inside the guest OS. On Linux these commands inspect current addresses and routes without changing them:
ip -brief address
ip -4 route
ip -6 route
Compare the assigned prefix with the addresses on the correct interface. If the operating system uses Netplan, NetworkManager or another manager, use that system's supported configuration method rather than mixing conflicting files. Ask support for the service's exact gateway/routing requirements when unclear.
DNS, reverse DNS and firewall are separate
- A DNS A record points a name to IPv4; AAAA points to IPv6. Create an AAAA record only after IPv6 connectivity and application listening are verified.
- Reverse DNS (PTR) maps an IP back to a name. Its separate panel entry does not replace forward DNS.
- Check IPv4 and IPv6 firewall policy. Opening one address family does not necessarily open the other.
- An application listening only on
127.0.0.1is not publicly reachable merely because the VPS has an IP. Check bindings before changing firewall rules.
If a connection stops working
Use the console to review and undo your last known change. Test IPv4 and IPv6 separately and record the affected address family, port, time and error. Do not disable every firewall or reassign arbitrary addresses as a troubleshooting shortcut. If the allocation is absent or the panel cannot load it, contact support with the billing Service ID. Avoid sharing session URLs or full unrelated address lists.
Sign out of the separate control panel when finished.
