On this page
The Network tab reports how your server is wired up: the interface it runs on, the addresses assigned to it, and the DNS resolvers it was given. Everything on this tab is a display. Nothing on it writes, so the sections below also give you the route that works for each change.
Primary network
The first card describes the interface itself.
| Field | What it is |
|---|---|
| ID | The interface's identifier on the hypervisor. |
| MAC | The hardware address of the interface. |
| Interface | The device name inside the server, usually eth0. |
| Type | Whether the interface is public or private. |
| Speed (inbound) | The inbound interface speed the hypervisor reports. |
| Speed (outbound) | The outbound interface speed the hypervisor reports. |
The two speeds are reported upstream in KB/s and shown here converted to Mbps or Gbps. A dash in any field on this tab means no value was reported for it.
Your addresses
IPv4 addresses and IPv6 addresses each list the addresses assigned to the server, with three fields per address.
- Address is the address itself with its prefix appended, for example
203.0.113.10/24. The prefix is the netmask in CIDR form, so/24is255.255.255.0. - Gateway is the router the server sends off-subnet traffic to.
- rDNS is the reverse DNS name on the address.
These are the values your server is configured with, and the ones to use if you ever set the interface up by hand from the console.
Reverse DNS is shown, not set here
The rDNS field is display only. There is no input next to it and no dialog behind it, so a reverse record cannot be created or changed from the panel. Most servers show a dash here, because the value only appears once a record has actually been set.
To set or change reverse DNS, open a ticket with the address and the hostname you want it to resolve to.
Addresses cannot be added or removed here
There is no control on this tab, or anywhere else in the panel, to allocate an extra address to a server or to release one. Both are support requests: open a ticket naming the server and what you need, and the team handles the allocation.
DNS resolvers
The Public DNS resolvers card shows the two resolvers configured on your address, as Primary and Secondary, each with a copy button. If a resolver is one of the well known public ones the panel names the provider, for example Cloudflare, Google, Quad9, or OpenDNS. Anything else is shown as Custom. A resolver that was never set reads System default.
The resolvers are stamped onto the address when it is allocated and cannot be swapped from the panel. Two routes work.
Change them on the server
Edit /etc/resolv.conf over SSH. This applies to the running server and takes
effect for lookups made after it:
sudo nano /etc/resolv.confThis is a change to the server's own configuration, so it does not survive a rebuild. Rebuilding wipes the disk and installs a fresh operating system, which comes back with the defaults.
Change the default for the address
Open a ticket and ask for the resolvers on your IP block to be updated. That changes the values new servers and rebuilds inherit, so the change sticks rather than needing to be reapplied after every reinstall.
Firewall and ports are on another tab
Nothing on the Network tab opens a port, closes one, or filters traffic. Port rules, rate limits, and IP blocking all live on the Firewall tab.