Your servers (VPS)
On this page
- Ordering a server
- Finishing a server we started for you
- Reserved IPv4 addresses
- After you order
- Changing plan
- Starting and stopping
- Console
- Screen
- Backups
- Graphs
- Snapshots
- Firewall
- Access
- The metadata service (169.254.169.254)
- Hatch: SSH to your servers
- Hardware
- Rescue and reinstall
- Network boot
- Network
- Primary addresses
- IPv4
- IPv6
- Null routes
- Reverse DNS
- Address registration (ARIN whois)
- Example (Ubuntu netplan)
- Example (Debian ifupdown)
- Example (AlmaLinux, Rocky Linux, CentOS Stream)
- Example (FreeBSD)
- Using your /64
- Through the API
A VPS is a virtual server of your own, with a plan's processors, memory and disk, and its own IPv4 and IPv6 addresses. Your servers are on the account page under Compute (see your account page).
Who sees them. Only the organization's owners and admins see its servers. Members and billing members don't.
Ordering a server
Owners and billing members order servers. Click Order a server on Compute (or + Compute in an organization's Add row under Organizations & billing) and choose:
- Plan: its processors, memory, disk and IPv4 addresses, billed monthly or yearly. The first period is billed now: from your organization's credit when it covers it (the page says so), otherwise with a saved payment method. Without either, the page shows your billing to save a method or add funds.
Image: the system to install, such as Debian 12, or Install later: the server is ordered and given its address now. Where the page says (boot into rescue mode), it is built empty straight away (a blank disk of the plan's size) and boots our rescue system, so you can sign in through Hatch's console and install whatever you like by hand; otherwise choose its system under Finish setting up on the server when you are ready. Either way you can install or reinstall it later.
Or, under Or boot an image, to install by hand, pick an image we offer, such as an installer (marked (installer)). The server is built empty and boots that image, and no SSH keys are needed. Open its console on its Rescue tab and install, then choose End rescue to boot what you installed. See Rescue and reinstall and Encrypting your server's disk.
- Access: the SSH public keys to sign in with, one a line. The keys you saved under Security → SSH keys are filled in; change them for this server if you like. A name, too, if you want one.
- IPv4 address: a new address from our pools, or one of the reserved addresses your organization holds. Every server gets IPv6 as well.
Click Order server. The server builds by itself, usually in a few minutes, and your organization's owners and admins get an email when it is ready. If the page says we set servers up by hand at the moment, it shows as being set up until we have.
Each server is a subscription of its own: change its plan on Compute, or Cancel it under Organizations & billing (it works until the end of the period paid for; Keep it takes that back). The first period (and an address you hold for it) is billed the moment you order, from your credit or your saved payment method, not later.
A link to a server plan from our site opens the same page with that plan chosen.
Finishing a server we started for you
When we start a server for you (from a quote, say), it shows on Compute as being set up, with a Finish setting up form for your organization's owners and admins: choose the image, your SSH keys and its IPv4 address, either one of the reserved addresses your organization holds or a new one (any address we already gave it is kept), then click Set up server. It gets IPv6 too and builds by itself, usually in a few minutes. You can pick an image to boot there too, as when ordering (Boot the image). Choose Install later there to give it its address now and the system another time (Save address).
Reserved IPv4 addresses
An organization can keep IPv4 addresses of its own, whether or not they are on a server: to move an address from one server to another, to put a known address on a new server, or to keep a server's address when the server goes. They are on Compute → Reserved IPv4 addresses.
- Hold an address (owners and billing members) takes a free address from our pools. Keep this address holds one already on one of your servers, so it stays yours when that server goes. Each address you hold costs $5.00 a month (the price shown on the page), billed when you hold it and every month after until you release it, on a server or not. An organization holds at most 32.
- Put on server (owners and admins) puts an address that is on no server on one of yours; the server takes it by DHCP, or bind it as the Network tab shows. Take off takes it off again: it stays yours.
- Cancel (owners and billing members) stops its charge. It stays yours until the end of the month already paid for (the list shows the date, and Keep it takes the cancellation back); then it is taken off its server, with its DHCP reservation, routes and firewall entry, and someone else may get it.
We may also reserve addresses for your organization ourselves (for example by agreement): those show here as reserved for you by us and are not charged on this page.
After you order
Each VPS subscription is one server, named "Server 1", "Server 2" and so on. It shows being set up while we prepare it; its buttons and addresses appear once it is ready, and your organization's owners and admins get an email saying so, with its addresses. To rename it, click Rename next to its name. The new name is only for you.
The page updates by itself. While it is open, the servers' state is read again every 15 seconds:
- Its power state (running or stopped), its use (CPU, memory, uptime, network) and the actions waiting their turn update in place.
- A server that finishes building, goes in or out of rescue, gets new addresses or changes plan is drawn again.
- A server you are typing in, or whose console or screen is open, waits until you're done, so nothing you're doing is lost.
- It pauses while the browser tab is in the background.
Signing in. If we built your server from one of our images, it comes with the SSH public keys you gave us. Sign in over SSH to its IPv4 address as the user we tell you, for example ssh debian@192.0.2.10. To use a password as well, set one on the server's Access tab. To add keys, add them to ~/.ssh/authorized_keys on the server, or change them on the Access tab. Lost your key? Set a new password or keys there.
Changing plan
When your server's plan changes (ask us for another plan), the server is set to the new plan's processors and memory, which it takes when it next starts, so restart it (Shut down, then Start) after changing.
Moving to a larger plan also grows its disk. The new space shows up at the end of the disk: grow the partition and file system to use it, for example growpart /dev/sda 1 and resize2fs /dev/sda1 (many cloud images do this by themselves at boot). Moving to a smaller plan never shrinks the disk.
Starting and stopping
Our images come with the QEMU guest agent, so shutting down is always clean and backups are consistent. On a system of your own, install qemu-guest-agent for the same.
Once the server is ready, these buttons appear (if your plan includes power controls):
| Button | What happens |
|---|---|
| Start | Turns the server on. |
| Shut down | Asks the server's system to shut down cleanly. If it hasn't stopped after three minutes, it is turned off. |
| Reboot | Asks the system to restart. |
| Stop | Turns the server off at once, like pulling the plug. Unsaved work is lost. |
| Reset | Restarts it at once, without shutting down first. Containers don't have this. |
Stop and Reset ask you to confirm first. Actions are a few seconds apart. Each one is recorded in your organization's activity.
Queued actions. While the server's host is busy with it (a shutdown waiting for the system to stop, or a backup), it can't take another change. Rather than failing, what you ask for then (a power action, starting or ending rescue, an access change) is queued: the page says so, shows what waits, and does each in turn as soon as the host has finished, within about 15 minutes. The same action can't be queued twice. If a queued action fails in the end, it is noted in your organization's activity.
If your plan includes status and usage, the server also shows its uptime and its CPU, memory, disk and network use.
Suspended servers. If a subscription is suspended, its server is shut down and can't be started until the subscription is active again. Over an unpaid invoice it goes in steps, each mailed to you: first the server loses its network but keeps running, then it is shut down, and later, depending on the provider, it is removed with everything on it. The server's card says which. Paying the invoice brings its network back at once (start it again if it was shut down); a removed server can't be brought back by paying, so pay before then. See Billing and tax.
Console
Every plan includes the console. Console next to the server's buttons opens its text console in the page: what you'd see on a serial cable plugged into it. Use it to sign in when the network is down, or to watch the server boot.
- Click into the console and type. Ctrl+Shift+C and Ctrl+Shift+V copy and paste; other Ctrl keys go to the server.
- If it stays blank, press Enter. A VM shows its first serial port (
ttyS0): most cloud images run a login there. If yours doesn't, turn it on withsystemctl enable --now serial-getty@ttyS0. - Every VM is given that serial port. If your server had none, it gets one the next time it is stopped and started: shut it down and start it from the account page (a reboot inside the server is not enough).
- Sign in with a password: the console has no SSH keys. Set one first with
passwdover SSH. - Close console closes it. A console closes by itself after eight hours, or if you stop being an owner or admin of the organization. At most three can be open on a server at once.
Opening the console is recorded in your organization's activity.
Screen
Screen, beside Console (VMs only), shows the server's screen, as a monitor plugged into it would: its graphical console. Use it for a boot menu or a system that shows nothing on the serial console, such as an installer with a graphical menu.
- Click the screen, then type; the mouse works too. Ctrl+Alt+Del above it sends that to the server.
- A server whose display is its serial port (as servers built from our images are) shows nothing on the screen: use Console, or start rescue on the screen (below), which gives it a standard display until rescue ends.
- It follows the console's rules: the console feature, owners and admins, eight hours at most, and the screen counts toward the three consoles a server may have open. Opening it is recorded in your organization's activity.
Backups
If your plan includes backups, the server's Backups tab lists them, newest first.
- Back up now takes a backup while the server keeps running. We keep your newest few (the number is shown); taking another removes the oldest beyond that.
- Restore puts a backup back over the server. Shut the server down first. Everything on it now is replaced by the backup and lost. Start it again once the restore has finished.
- Delete removes a backup for good. Backups marked kept were kept by us and can't be deleted here.
You can take or restore a backup once every ten minutes. A backup taken while the server is running is like pulling the plug at that moment: databases recover from it, but for a clean copy, shut the server down first or stop the database.
Graphs
If your plan includes usage graphs, the server's Graphs tab shows its CPU, memory, network and disk use over the last hour, day, week, month or year (pick one above the graphs). Each point is the average over a short step: a minute for an hour, half an hour for a day, a day for a year. Hover over a graph (or tab to it) to read the values at a time; Show as a table lists them all. CPU is a share of all the server's vCPUs, so 100% means every one was busy. A gap means the server was stopped.
Snapshots
If your plan includes snapshots, the server's Snapshots tab lists them, newest first, with how many your plan lets you keep.
- Take a snapshot saves the server's disks as they are now. Give it a name (a letter, then letters, digits,
-and_, up to 40) and a note if you like; without a name it is called after the time, such assnap-20261107-142500. Tick Save the running memory too to save a running server's memory as well: rolling back then resumes it running, exactly where it was. That takes longer and more space. - Roll back puts the server back as it was at that snapshot. Everything on it since is lost. Without saved memory the server is stopped afterwards: start it again.
- Delete removes a snapshot. The server keeps what is on it now.
You can take or roll back a snapshot once every two minutes. A snapshot is a quick way back before an upgrade or a risky change, not a backup: it lives on the same storage as the server's disks, and many or old snapshots slow the disks down, so delete them once you are done.
If you moved to a smaller plan, you can't roll back to a snapshot taken on the bigger one (it would bring back its vCPUs and memory); ask us. After any rollback, your plan's vCPUs and memory are put on the server again.
Firewall
Every server has a firewall (Proxmox's own, in front of the server, so it works whatever runs inside). Open the server's Firewall tab to set it up:
- Policies: what happens to traffic no rule matches, coming in and going out (ACCEPT, DROP or REJECT), what is logged, and whether DHCP and IPv6 neighbour discovery (NDP) are let through. The firewall itself stays on: to let everything through, set both policies to ACCEPT.
- Rules, checked from the top; the first that matches decides. A rule is a direction (in or out), an action, and what it matches: a macro such as
SSH,HTTPorDNS, or a protocol (tcp,udp,icmp...) with ports (22,80,443,8000:8100), and where from or to (an address, a network, an alias or+an IP set). Add one at the bottom, move it up or down, turn it off or on, or remove it. - Aliases name an address or network to use in rules.
- IP sets group addresses and networks; use one in a rule as
+name.
Two things are ours and locked:
- Your addresses. The server can only send from, and be reached on, the addresses it has been given (shown at the top). This stops anyone using an address that isn't theirs. When you get a new address it is added for you.
- Outgoing mail (port 25) is blocked on every server, to keep spam off our network; its rule stays at the top. Mail you send through a mail provider on port 587 or 465 is not affected. To have port 25 opened, choose Ask to open port 25 on the Firewall tab and say what the server sends mail for and how you keep it from sending spam. That becomes your support request (the Support section of your account): we answer there, and once we approve it port 25 is open. One request waits at a time; if we say no, the answer shows on the tab and you can ask again.
- Rules support locked. Support may lock a rule on your server, such as one blocking a port it was abused through. It sits at the top with ours, with a lock and support's note as its comment. You can't change, move or remove it; open a support ticket if it is in your way.
Rules you add always go below ours. A rule that copies ours (its comment starting zappocity:) or uses our address list is refused.
Access
A server's Access tab sets how you sign in to it: its hostname, the user it makes, the SSH keys that user accepts, and a password, as well as its name servers, search domains and whether packages are upgraded when it first starts. These are set by cloud-init when the server starts, so a change is taken on at its next start, power on or reboot from your account page. A reboot from inside the server does not pick it up. Tick Reboot now to take a change on at once.
- Hostname: letters, digits and hyphens, in labels separated by dots, such as
web1orweb1.example.com. - User: the user cloud-init makes, such as
debian, orroot. - SSH keys: public keys, one a line (at most 20). Leave it empty to remove them all.
- Password: type one (12 to 128 characters), or leave it empty and we make a random one. A password we make is shown once, on the tab, with a copy button. We never keep a password or record it: if you lose it, set a new one.
- Name servers: the DNS resolvers the server uses, up to three IPv4 and three IPv6 addresses separated by spaces, such as
9.9.9.9 2620:fe::fe. Leave it empty for the ones we give out. - Search domains: the domains short names are looked up in, such as
example.com(up to six). - Upgrade packages at first boot: on unless you turn it off.
cloud-init treats changed settings as a new setup of the server when it next starts, as with any cloud-init drive: it makes new SSH host keys (your SSH client warns that the server's key changed) and sets the password again if one is set.
The tab is there for servers that are VMs. A container's access is set inside it. A server built without a cloud-init drive says so; set its access inside it, or open a support ticket.
The metadata service (169.254.169.254)
Many of our servers take their cloud-init settings from a metadata service at 169.254.169.254, the address cloud servers use, in place of a cloud-init drive. The settings are the Access tab's (hostname, user, SSH keys, password) plus your addresses and name servers.
How cloud-init finds it. cloud-init reads the server's SMBIOS serial ds=nocloud;s=http://169.254.169.254/nocloud/ at boot. Every current cloud image does this: Ubuntu, Debian, Fedora, Rocky, Alma, openSUSE and Arch. A system installed from an ISO without cloud-init gets nothing from it.
What it serves. It answers your server only, and nothing else:
meta-data,user-dataandnetwork-configunder/nocloud/, in cloud-init's NoCloud format.network-configputs your addresses (routed IPv4 ones as/32s) on your network card.- AWS-style requests (
/latest/meta-data/...), for tools that expect them. These need an IMDSv2 token first, fromPUT /latest/api/token. They never include your password.
To look from your server:
curl -s http://169.254.169.254/nocloud/meta-data
curl -s http://169.254.169.254/nocloud/network-config
cloud-init query ds # NoCloud, seeded from the address
TOKEN=$(curl -s -X PUT http://169.254.169.254/latest/api/token -H "X-aws-ec2-metadata-token-ttl-seconds: 60")
curl -s -H "X-aws-ec2-metadata-token: $TOKEN" http://169.254.169.254/latest/meta-data/
Your password. The password's hash is handed out once, on the first boot after it is set, and never again. A program on your server can't read it later. If a password didn't take (say the first boot crashed), set it again on the Access tab.
When a change arrives. An Access change reaches the service within a minute. A reboot sooner than that may start with the old settings, so reboot once more. cloud-init treats a changed server as a new one, so its SSH host keys change, as they do with a drive.
Keep the address reachable. If your firewall inside the server blocks outgoing connections, allow TCP port 80 to 169.254.169.254.
The network helper. Servers with more than one address run a small helper (proxmox-network-helper, every few minutes) that puts the addresses from the metadata service on the server. It keeps itself up to date: when the metadata names a newer one, it downloads it from us over HTTPS and uses it only if its SHA-256 checksum matches. To turn that off, put AUTO_UPDATE=0 in /etc/default/proxmox-network-helper (and allow outgoing HTTPS if you'd like it to stay on).
Hatch: SSH to your servers
Compute starts with Hatch, our emergency shell for the servers you manage: their console, power, rescue mode and reinstall over SSH, even when a server can't be reached. The card shows the line to sign in with and the host key to check the first time. Hatch signs you in with an SSH key: Add an SSH key takes you to Security → SSH keys. See Hatch, the emergency shell for how to use it.
Hardware
The server's Hardware tab (owners and admins) shows how its virtual machine is set up and lets you choose its firmware.
- Firmware. UEFI, which new servers start with, or BIOS (legacy), for older systems that only start that way. A system installed for one may not start with the other. Our cloud images and most installers start with both, but an existing installation without an EFI system partition won't start with UEFI: switch back if it doesn't.
- Secure boot (UEFI only): only boot loaders signed with Microsoft's keys start. Ubuntu, Debian, AlmaLinux, Rocky and Fedora are signed; most rescue images aren't, so turn it off before booting one. Turning it on or off resets the firmware's boot entries, and the system starts from its fallback boot loader.
- Disks have SSD emulation, discard (deleted space is given back, with
fstrim) and an IO thread; NUMA is on; a serial port carries the console. We set these on every server. - Guest agent is on for every server, so it shuts down cleanly, shows its addresses and takes consistent backups. It needs
qemu-guest-agentrunning in the server: our images have it; on a system you installed yourself, install it (apt install qemu-guest-agentordnf install qemu-guest-agent) and start it (systemctl enable --now qemu-guest-agent). Answering means it works; not answering means it isn't installed or running there.
A firmware change needs the server stopped. If it is running, the tab offers to shut it down, change it and start it again. The change is recorded in your organization's activity.
Rescue and reinstall
A server's Rescue tab has two parts: booting from a rescue image, and reinstalling. Both are for servers that are VMs. Each is offered when your plan includes it, and either can be used once every few seconds.
Rescue mode boots the server into our rescue system (such as Finnix, a small Linux with repair tools) instead of its own, with your disks attached. Use it to repair a server that no longer boots, check its disks, or reset a password from outside it.
- Choose Turn rescue mode on. The server is started, or, if it is running, shut down and started again (a reboot alone wouldn't pick up the change; it is stopped if its system hasn't shut down within three minutes).
- Work in it right on the Rescue tab: Open console there opens the server's serial console in the page (press Enter if it stays blank).
- Or reach it through Hatch: the Rescue tab shows the line to sign in with (
ssh -p ...), then choose the server and its console. Hatch signs you in with your SSH key; add it under Security → SSH keys. - For SSH straight to it, in the console run
passwd(to set root's password) andsystemctl start ssh, thenssh root@the server's address, shown on the tab. - It stays in rescue mode across reboots until you choose Turn rescue mode off: the server then boots from its own disk again.
The rescue system stays in the server's CD drive, behind its disk, so turning rescue mode on and off only changes which it boots first.
Other images we offer, such as installers, boot the same way:
- Pick the image under Or boot the server from another image and choose Boot from it. The server is started, or shut down and started again if it is running.
- Choose how to work in it: on the serial console or on the screen. Each image starts on the one it suits; change it before booting. On the serial console its boot menu shows there; on the screen the server gets a standard display while it boots the image, and nothing needs adding at the boot menu. Either way its display is put back when rescue ends. Rescue mode has the same choice. Use the serial console unless it doesn't work for you: on the screen, our rescue system boots as published, without the serial console.
- Open the Console (or Screen) to work in the image. If the tab says what to do at its boot menu (such as adding
console=ttyS0,115200to the kernel line with Tab or e), do that first: without it some systems show nothing on the console. - The server keeps booting from the image, across reboots, until you choose End rescue. That takes the image out and boots the server from its own disk again.
- Images marked (installer) install a system of your own over the console, such as one with an encrypted disk. See Encrypting your server's disk.
Reinstall erases the server and installs it again from one of our images:
- Erased: its disks and snapshots. Backups stay.
- Kept: its addresses and the SSH keys it had.
You type the server's name to confirm. The server shows as being set up until it's ready, which usually takes a few minutes. To sign in with a password afterwards, set one on the Access tab.
Network boot
A server's Network boot tab boots it from the network into netboot.xyz's menu. From there you can install or run many systems (Debian, Ubuntu, Alpine, Rocky Linux, the BSDs, rescue tools and more) without an image of each. It's offered when your plan includes it and we've set it up, for servers that are VMs.
- Choose Boot from network. The server is started, or, if it is running, shut down and started again, once our DHCP servers have taken the change (usually within a minute).
- Open the Console to use netboot.xyz's menu. Some systems show their installer on the Screen instead.
- Your disks stay attached, so an installer can install onto them. Installing a new system erases what is on the disk it installs to.
- netboot.xyz's own program comes from us, checked against the copy we chose. What you pick in its menu is downloaded from that project's servers over the internet.
- The server boots from the network at every start until you choose Boot from disk. That restarts a running server from its own disk.
Network boot and rescue mode can't be on together; turn one off first.
Network
Each server's card has tabs: Network (its addresses), Reverse DNS (their names, with how many are set) and, if your plan includes them, Graphs, Backups, Snapshots and Firewall. Under Network, How to set the network up shows ready-made netplan, ifupdown, NetworkManager and FreeBSD setups for your addresses.
Primary addresses
A server with several addresses has one primary IPv4 and one primary IPv6: the address it is known by. It is listed with a primary badge, shown first, and given to the server as its public address in its metadata (public-ipv4, public-ipv6). Owners and admins choose it under Network, with the star beside another of the server's addresses; for IPv6, Primary from the /64 makes an address of your /64 the primary (the management address is the primary until then).
DHCP gives your server one IPv4 address, marked given by DHCP: the primary when it is on-link, else your management address (a routed primary comes through it). Every other address is set by hand, or by the network setup the metadata service gives the server, as in How to set the network up. A primary IPv6 from the /64 is set by hand too (as a /128 on lo); DHCPv6 keeps giving the management address.
Only the server's own addresses can be chosen. An address taken away from the server stops being its primary, and the default comes back. Changing the primary of a running server changes what DHCP gives it at its next lease: change its own network setup to match.
IPv4
An address is either on-link or routed:
- On-link addresses are on our network. Each is shown with its prefix length and gateway, for example
192.0.2.10/24, gateway 192.0.2.1. Put it oneth0with that prefix, by hand, or take it by DHCP: the address is kept for your server and is the one DHCP hands out. - Routed addresses are marked routed: see below.
Routed IPv4 addresses
Some addresses are routed to your server rather than on its network, the way your IPv6 /64 is. Your server then also has an IPv4 mgmt (management) address, such as 10.255.0.10/24, gateway 10.255.0.1.
- The management address is your server's place on our network. Set it up with its gateway as your default route, by hand or by DHCP.
- Each routed address, such as
203.0.113.10, reaches your server through the management address. Put it onlo(or adummy0interface) as a/32, and keep only the management address oneth0. It needs no gateway of its own: what you send from it goes out the same default route. - Servers we build set the management address up for you. If your server uses our metadata service, the routed addresses are added too. Otherwise add them as in the examples below.
ethernets:
eth0:
addresses:
- 10.255.0.10/24 # management address
routes:
- to: default
via: 10.255.0.1
lo:
addresses:
- 203.0.113.10/32 # routed to you
How to set the network up on the Network tab shows this with your own addresses.
IPv6
Your server gets two things:
- A management address in a shared network, for example
2001:db8:ffff::100/64, with its gateway (for example2001:db8:ffff::1). Set them up by hand (or by DHCPv6, below). - A /64 of its own, for example
2001:db8:1000:1::/64, routed to your management address. Use any address in it on the server, or hand it on to containers or VMs inside your server.
On some of our networks IPv6 comes in on a second network card (eth1, often named ens19), with IPv4 on the first. The account page says so, and its netplan and ifupdown examples put the IPv6 management address and its default route on that card.
If the account page says IPv6 can be taken by DHCPv6, you can instead let the server ask for both: the management address, and your /64 as a delegated prefix (dhcp6: true in netplan; for the prefix, a DHCPv6 client that asks for prefix delegation, such as systemd-networkd with [DHCPv6] PrefixDelegationHint=::/64). The default route comes from our router's advertisements.
Null routes
A null route makes our routers drop all traffic to one of your server's addresses before it reaches the server, as you might want when that address is under a denial-of-service attack. The server keeps running and its other addresses still work; the null-routed one can't be reached from anywhere until the null route is lifted.
On the server's Null routes tab (owners and admins), enter one of the server's addresses (an IPv4 address it has, or an address or prefix from /64 to /128 inside its IPv6 /64), with a reason if you like and, optionally, when it should end by itself. It takes effect within about a minute. Lift takes it away again.
Our support team may also null-route an address of yours, for example to stop an attack reaching our network; it shows on the same tab, put by "support", with their reason. Only support can lift those: open a ticket when you want one lifted.
A null route belongs to the address on that server: if the address is taken off the server, your null route stops with it.
Reverse DNS
The server's Reverse DNS tab lists each of its addresses with its name, such as mail.example.com: what the address looks up to (its PTR record). Mail servers often check this. Name it (or Edit) on an address sets its name in place; Remove clears it; Another address of your /64 names any other address in it.
- First add an A record (for IPv4) or AAAA record (for IPv6) for the name, pointing at the address. We only accept a name that already resolves to the address.
- You can name your IPv4 addresses, your management address, and up to 32 addresses in your /64.
- To remove a name, click Remove (or clear it and save).
- If the box isn't there, reverse DNS isn't offered for your addresses yet.
Your own name servers for your /64
Instead of setting names here one by one, you can keep every name in your /64 on name servers of your own. Under Reverse DNS → Name servers for your /64, list two to eight of them (such as ns1.example.com) and save: we point your /64 at them (NS records in our reverse zone), and they answer for every address in it.
- Each name server must already resolve (have an A or AAAA record).
- The names set here in your /64 go when you delegate it, and new ones are refused while it is delegated: set them on your name servers.
- dnso.city's name servers work too: first add your /64's zone (such as
1.0.0.0.0.0.0.1.8.b.d.0.1.0.0.2.ip6.arpafor2001:db8:1000:1::/64; the box shows yours) to a DNS account of yours on dnso.city, then delegate to dnso.city's name servers. Only those who manage the server can add that zone. As dnso.city signs it, its DS record is put beside the delegation, so DNSSEC carries on into it. See DNS hosting. - Remove the delegation to go back to setting names here. The delegation also goes when your /64 is taken back.
- Only the organization's owners and admins delegate, while the server is active.
Address registration (ARIN whois)
Your server's addresses belong to us at ARIN, the regional internet registry for North America. We may register them there as reassigned to you, so that whois shows who uses them. Under Your organizations → Address registration on the account page, choose how you appear:
- Private (the default): ARIN shows "Private Customer" with only the city, state, postal code and country of your billing address.
- The organization's name and billing address: shown in full.
Only owners change it; admins can see it. Changes reach ARIN within minutes, and a change of billing address is sent too. The box lists the addresses registered and their state. When an address goes back to us, its registration is removed.
Example (Ubuntu netplan)
Put this in /etc/netplan/50-zappocity.yaml, then run netplan apply:
network:
version: 2
ethernets:
eth0:
addresses:
- 192.0.2.10/24
- 2001:db8:ffff::100/128 # management address
routes:
- to: default
via: 192.0.2.1
- to: default
via: 2001:db8:ffff::1
on-link: true
lo:
addresses:
- 2001:db8:1000:1::1/128 # from your /64
The management address is a /128: the gateway is reached on the link (on-link), and addresses of your /64 go on lo, since they are routed to you rather than on our network.
Example (Debian ifupdown)
The same in /etc/network/interfaces:
auto lo
iface lo inet loopback
up ip -6 addr add 2001:db8:1000:1::1/128 dev lo
auto eth0
iface eth0 inet static
address 192.0.2.10/24
gateway 192.0.2.1
iface eth0 inet6 static
address 2001:db8:ffff::100/128
up ip -6 route add 2001:db8:ffff::1 dev eth0
up ip -6 route add default via 2001:db8:ffff::1 dev eth0
A routed IPv4 address goes on lo the same way: up ip addr add 203.0.113.10/32 dev lo.
Example (AlmaLinux, Rocky Linux, CentOS Stream)
These use NetworkManager. Run the commands as root from the console, since the connection drops while it changes. First take the old connection off the card: nmcli connection show lists them, and nmcli connection delete NAME removes one.
nmcli connection add type ethernet ifname eth0 con-name zappocity \
ipv4.method manual ipv4.addresses "192.0.2.10/24" ipv4.gateway 192.0.2.1 ipv4.dns 1.1.1.1 \
ipv6.method manual ipv6.addresses 2001:db8:ffff::100/128 \
ipv6.routes "2001:db8:ffff::1/128, ::/0 2001:db8:ffff::1" ipv6.dns 2606:4700:4700::1111
nmcli connection add type dummy ifname dummy0 con-name zappocity-routed \
ipv4.method disabled ipv6.method manual ipv6.addresses 2001:db8:1000:1::1/128
nmcli connection up zappocity && nmcli connection up zappocity-routed
- The IPv6 gateway. The management address is a
/128, so the first route reaches the gateway directly on the card, and the second makes it the default route. - What is routed to you goes on a
dummy0device rather thanlo: the address from your /64, and any routed IPv4 address, such asipv4.method manual ipv4.addresses "203.0.113.10/32"in place ofipv4.method disabled. - IPv6 on its own card. Put the IPv6 parts on a second connection on
eth1, withipv4.method disabled, and useipv6.method disabledoneth0.
Use your own addresses from the account page. The interface may be named ens18 rather than eth0; ip link shows its name.
Example (FreeBSD)
Add these lines to /etc/rc.conf, replacing the card's old ifconfig_ lines. Put nameserver 1.1.1.1 in /etc/resolv.conf. Then run service netif restart && service routing restart from the console:
ifconfig_vtnet0="inet 192.0.2.10/24"
defaultrouter="192.0.2.1"
ifconfig_vtnet0_ipv6="inet6 2001:db8:ffff::100/128"
ipv6_static_routes="zgw zdefault"
ipv6_route_zgw="2001:db8:ffff::1 -prefixlen 128 -interface vtnet0"
ipv6_route_zdefault="default 2001:db8:ffff::1"
ifconfig_lo0_alias0="inet6 2001:db8:1000:1::1/128"
- The card. FreeBSD names the card
vtnet0.ifconfiglists the cards. - The IPv6 gateway. The management address is a
/128, so the gateway is reached through a host route on the card (zgw). That route comes before the default route. For this reason the routes are named inipv6_static_routesrather than set withipv6_defaultrouter. - What is routed to you goes on
lo0as aliases, numbered from 0. A routed IPv4 address is one more alias, such asifconfig_lo0_alias1="inet 203.0.113.10/32". - IPv6 on its own card. Put the IPv6 lines on
vtnet1, and addifconfig_vtnet1="up".
Using your /64
Every address in your /64 reaches your server; the first one (2001:db8:1000:1::1 in the examples) is set up above. How to set the network up on the account page shows these with your own addresses.
- More addresses, one by one. Add each as a /128, in netplan's
addressesunderlo(- 2001:db8:1000:1::2/128) or at once withip -6 addr add 2001:db8:1000:1::2/128 dev lo. On FreeBSD, useifconfig lo0 inet6 2001:db8:1000:1::2/128 alias. To keep it, add it as the nextifconfig_lo0_aliasline in/etc/rc.conf. Every address at once. A local route makes your server answer on the whole /64, so a program can listen on any address in it without adding each one:
ip -6 route add local 2001:db8:1000:1::/64 dev loTo keep it with NetworkManager:
nmcli connection modify zappocity-routed +ipv6.routes "2001:db8:1000:1::/64 type=local". With netplan, add it underloasroutes:- to: 2001:db8:1000:1::/64 type: local scope: hostHanded on to containers or VMs. Put
2001:db8:1000:1::1/64on their bridge (such aslxdbr0orvmbr0) instead of2001:db8:1000:1::1/128onlo, and turn forwarding on:echo net.ipv6.conf.all.forwarding=1 > /etc/sysctl.d/90-ipv6-forward.conf sysctl --systemEach container takes its own address of the /64 with
2001:db8:1000:1::1as its gateway. With forwarding on, your server ignores our router's advertisements, so keep its default route set by hand. Use this or the local route, not both.
To check: ip -6 route get 2606:4700:4700::1111 goes via your gateway, and ping -6 to an address of your /64 from elsewhere answers. Your /64 needs no route or gateway of its own: we route it to your management address.
Through the API
GET /api/account/orgs/{orgId}/servers lists the servers, and POST .../servers/{serverId}/power with {"action": "start"} (or shutdown, stop, reboot, reset) acts on one. Both use your signed-in session. See the account API.