Network Information

Everything you need to know about networking on vps.direct virtual servers.

This page explains the default network setup, public IP handling, IPv6 availability and common operating system examples for adding extra IP addresses.

Overview

vps.direct is designed for low-latency, reliable VPS hosting with modern network connectivity across supported locations.

Port Capacity

Most VPS Direct virtual servers are connected through a shared network port.

This means your server can burst up to the advertised port speed when capacity is available, but the port is shared with other users on the same infrastructure. Sustained usage, abusive traffic, or activity that negatively impacts other customers may be rate-limited according to our fair use policy.

For customers who require guaranteed throughput, private networking, or custom bandwidth commitments, please open a ticket before ordering.

Looking Glass

Our Looking Glass allows you to test connectivity from VPS Direct network locations.

You can use it to:

• Run ping and traceroute tests
• Check routing from specific locations
• Compare latency before ordering
• Verify upstream connectivity
• Diagnose route-specific issues

Open the VPS Direct Looking Glass

IPv6

IPv6 is supported on eligible VPS Direct services and locations.

Depending on the product, your service may receive either:

• A single IPv6 address
• A routed IPv6 subnet
• A larger IPv6 allocation by request

You can find the assigned IPv6 details in the client area or inside your VPS welcome email.

Common IPv6 Details

Additional IPv4 Addresses

Additional IPv4 addresses may be available depending on stock, location, and justification.

After an additional IPv4 address has been assigned to your service, it may need to be configured manually inside the operating system.

The examples below assume the main network interface is eth0.

Configure an Additional IPv4 on Ubuntu

Most modern Ubuntu templates use Netplan.

Create a new Netplan file:

sudo nano /etc/netplan/99-additional-ip.yaml

Add the following configuration:

network:
  version: 2
  ethernets:
    eth0:
      addresses:
        - YOUR_ADDITIONAL_IPV4/32

Apply the configuration:

sudo netplan apply

Verify that the address is active:

ip addr show eth0

Multiple Additional IPv4 Addresses on Ubuntu

network:
  version: 2
  ethernets:
    eth0:
      addresses:
        - YOUR_ADDITIONAL_IPV4_1/32
        - YOUR_ADDITIONAL_IPV4_2/32
        - YOUR_ADDITIONAL_IPV4_3/32

Then apply:

sudo netplan apply

Configure an Additional IPv4 on Debian

On Debian systems using /etc/network/interfaces, create a separate interface configuration file:

sudo nano /etc/network/interfaces.d/99-additional-ip

Add the following:

auto eth0
iface eth0 inet static
    address YOUR_ADDITIONAL_IPV4/32

Restart networking:

sudo systemctl restart networking

Verify the address:

ip addr show eth0

Multiple Additional IPv4 Addresses on Debian

auto eth0
iface eth0 inet static
    address YOUR_ADDITIONAL_IPV4_1/32
    address YOUR_ADDITIONAL_IPV4_2/32
    address YOUR_ADDITIONAL_IPV4_3/32

Then restart networking:

sudo systemctl restart networking

Reverse DNS

Reverse DNS, also known as rDNS or PTR, maps an IP address back to a hostname.

You may need rDNS for:

• Mail servers
• Monitoring systems
• Compliance checks
• Cleaner network identification

Recommended format:

server-name.yourdomain.com

Before requesting rDNS, make sure the hostname already resolves forward to the same IP address.

Troubleshooting

If your VPS has network connectivity issues, check the following first:

Useful commands:

ip addr
ip route
ping 1.1.1.1
ping google.com
traceroute 1.1.1.1
mtr 1.1.1.1

If DNS resolution fails but pinging an IP works, check /etc/resolv.conf or your system resolver configuration.

When to Contact Support

Open a support ticket if:

• Your assigned IP address does not route
• The gateway is unreachable
• IPv6 is missing from your service details
• You need rDNS configured
• You see packet loss from multiple external networks
• You need confirmation before ordering a custom network setup

When contacting support, include:

• Service ID
• Affected IP address
• Operating system
• Network location
• Screenshots or command output
• MTR or traceroute results, if available