Manage an instance's addresses and names

The Network tab shows the IP addresses that reach an instance, the floating IPs attached to it and the traffic it has used this month. From the tab you can also give the instance a name in one of your domains, set the reverse DNS of each address and put a web address in front of it.

Each instance comes with one IPv4 address, its primary address. An instance in a location with IPv6 also has an IPv6 /64 of its own, at no charge, as Add IPv6 to an instance describes. More addresses are floating IPs that you order and attach.

To name the instance, you need a DNS zone on your account in Coritan DNS. That can be your own domain, as Add a domain you already own describes, or a free name under coritan.gg, as Claim a free coritan.gg name describes.

In the dashboard, go to Cloud Compute, open the instance and select the Network tab.

Addresses

Every address that reaches the instance: the primary address, then the instance's IPv6 address and its IPv6 /64, then the other addresses attached to it. Each row shows the Address, its Gateway, its Role and Since when it has been attached. The primary address and each floating IP show their version and prefix length under the address. The primary address shows Primary under Role. Select Copy address to copy an address, or Copy IPv6 address and Copy IPv6 /64 on the IPv6 rows. An instance with no IPv6 shows This instance has no IPv6 yet. under the list, with Add IPv6….

Floating IPs

The floating IPs on your account that are attached to the instance, with their Region and Since date. Select an address to open it on the Floating IPs page, or Reverse DNS to open its reverse DNS. Below them, the card lists the floating IPs on your account that are not attached yet, and subnet blocks with a free host, each with Attach. Order floating IP opens the order page for this instance.

Interfaces

The instance's virtual network cards. Each shows its MAC address, which Copy MAC address copies, and its model and port speed.

Traffic

How much the instance has sent and received this month, against its plan's allowance. How instance traffic is counted explains the figures.

1. On the Floating IPs card, select Attach beside an address that is not attached yet. The address opens on the Floating IPs page, with this instance chosen on its Attach tab.
2. For a subnet block, choose the Host address, or keep First free host. Then select Attach address. Attach and detach a floating IP describes the rest of the form.
3. Restart the instance from the header. The instance sets up the new address when it starts, as Start, stop and restart an instance explains.

The address then appears on the Addresses card. If you have no floating IP to attach yet, select Order floating IP on the card, or order one from the Floating IPs page.

An instance can have an IPv6 /64 of its own, at no charge: a block of IPv6 addresses that we route to it. The instance uses the first address in the /64, such as 2001:db8:1000:5::1, as its IPv6 address, with fe80::1 as its IPv6 gateway. Every other address in the /64 reaches the instance too.

An instance created in a location that has IPv6 gets its /64 when we create it. To add IPv6 to an instance that has none, such as one created before its location had IPv6:

1. On the Network tab, find This instance has no IPv6 yet. under the Addresses card's list, and select Add IPv6….
2. Check the instance's name in the dialog, then select Add IPv6.
3. Restart the instance from the header, or start it if it is stopped.

The message IPv6 added. Restart the instance to use it. confirms that the instance has its /64. If we cannot give it one, a message that starts Could not add IPv6: gives the reason, and nothing changes on the instance. Troubleshooting lists the reasons.

The Addresses card then lists the IPv6 address with fe80::1 under Gateway, and the IPv6 /64 with Routed under Role and IPv6 /64 · Comes with this instance and stays with it. under it. The header shows the IPv6 address beside the IPv4 address, and Copy IPv6 address copies it.

A floating IPv6 address attaches as Attach another address describes. The instance takes it as a single address, a /128, beside its /64 when it next starts.

The instance sets up its IPv6 address when it starts from the dashboard. Cloud-init in the image gives its first network interface the address with the prefix length /64 and a default IPv6 route through fe80::1, as it does for the primary address. You install nothing, but the address works only after such a start:

• A new instance starts before we give it its /64. Restart it from the header once it is ready.
• After Add IPv6, restart it from the header, as step 3 says.
• A reboot typed inside the instance does not set the address up, as Start, stop and restart an instance explains.

After the restart, ip -6 addr inside the instance lists the IPv6 address, and ip -6 route shows default via fe80::1. The other addresses of the /64 reach the instance too, and it answers on each one once you add it to its network interface.

The Name this instance card gives the instance a hostname in a zone you hold, such as vm.example.com. It writes an A record for each IPv4 address and an AAAA record for each IPv6 address attached to the instance.

1. On the Network tab, find the Name this instance card.
2. Under DNS name, type the full name, such as vm.example.com. If you hold a coritan.gg name, the field already holds a name under it, and selecting one of the names listed under the field fills it in.
3. Leave Set reverse DNS to match ticked to set the same name as the reverse DNS of the primary address. Mail servers expect it there.
4. Tick Set the hostname too to make the first part of the name the instance's hostname, such as vm for vm.example.com. The instance takes it when you next start or restart it from the dashboard. The Settings tab changes the hostname on its own, as Rename the instance describes.
5. Select Name this instance.

The card confirms which records it wrote. Records the name already had stay in the zone, so remove any that point elsewhere on the zone's DNS page, as Add, edit and delete DNS records describes. We write the new records with a TTL of 300 seconds.

Reverse DNS is the name a lookup of an address returns. Mail servers compare it with the name your mail server gives when it connects, so set it on any address that sends mail. Set it to a name that resolves back to the same address.

1. On the Reverse DNS card, find the address and select Edit.
2. Type the full name, such as mail.example.com.
3. Select Save.

The card shows the new name next to the address. The name must be a full domain name with at least one dot.

The card lists the instance's IPv6 address beside its IPv4 addresses. To set reverse DNS for another address in the instance's /64, such as 2001:db8:1000:5::25:

1. In the dashboard, go to Floating IPs. Its card shows the /64 with IPv6 /64 in the line under the address, and Comes with and the instance's name under Attached to.
2. Open the /64 and select the Reverse DNS tab.
3. Under Address, type the address. The field takes any address inside the /64, and starts on the instance's IPv6 address.
4. Type the full name in the field under it, then select Save reverse DNS.

The /64 keeps up to 256 names. Set reverse DNS for a floating IP explains the Published record preview and the messages the tab shows.

The Web address card creates a web proxy for a site on the instance. The proxy answers at a hostname you choose and forwards the requests to port 80 of the primary address, with HTTPS and the WAF in front.

1. On the Web address card, type the Hostname, such as www.example.com.
2. Leave Request an HTTPS certificate ticked to get a certificate for the name.
3. Select the button under the form, "Give this instance a web address".

When we host the name's zone, we write its DNS record for you. The card then lists the web address with Manage route, which opens it in Game Shield. Create a web proxy covers the options.

The Addresses card lists each address on the instance, the name you chose resolves to the instance's addresses, and the Reverse DNS card shows the name each address answers with.

No addresses yet

The instance has no address attached. Attach a floating IP, then restart the instance from the header.

A new address does not answer

The instance sets up addresses when it starts, its IPv6 address included. Restart it from the header, as the steps above describe. A reboot typed inside the instance does not set them up.

Could not add IPv6: This location has no IPv6 yet.

The instance's location does not offer IPv6. Nothing changed on the instance.

Could not add IPv6: This location has no IPv6 left to give out. Contact support.

Contact support with the instance's name.

Could not add IPv6: We could not add IPv6 to this instance. Try again in a moment.

The instance did not get its /64, and nothing changed on it. Select Add IPv6… again in a moment.

Could not add IPv6: Instance is migrating

We are moving the instance to another host. Add IPv6 once the move has finished.

This instance already had IPv6.

The instance got its /64 while the page was open, for example from another tab. The Addresses card now lists it.

This /64 comes with its instance and stays with it.

You tried to detach or move the instance's /64. It stays with the instance until the instance ends.

Enter a full hostname inside a zone you hold, such as vm.example.coritan.gg.

Type the whole name, including the domain, such as vm.example.com.

Use a name inside a domain you hold here, or claim a platform name first

The name is not inside a DNS zone on your account. Add the domain to Coritan DNS, or claim a coritan.gg name, then try again.

A message that starts The guest hostname is the first part of the name.

Set the hostname too was ticked, and the first part of the name cannot be a hostname, for example because it holds an underscore. We saved nothing. Untick the box, or choose a name whose first part uses only letters, digits and hyphens.

A message that ends is a CNAME; pick another name or remove that record first

The name already has a CNAME record, which cannot sit beside an A record. Choose another name, or delete the CNAME record in the zone first.

This instance has no address yet

Attach an address to the instance before you name it.

Could not set reverse DNS: PTR hostname must be a fully-qualified domain name

Type a full name with a domain, such as mail.example.com, not a single word.

A reverse lookup still returns the old name

Resolvers can keep the old answer for a few minutes. If the old name stays for longer, contact support with the address.

• Floating IPs covers ordering, attaching and moving addresses.
• Set reverse DNS for a floating IP sets reverse DNS from the Floating IPs page, including the hosts of a subnet.
• How instance traffic is counted explains the Traffic card.
• How DNS hosting works explains the zones the name goes in.

GET /api/v1/client/vps/{uuid}/ips lists the addresses attached to the instance, primary first. Each has the address, prefix_len, subnet_mask, gateway, is_primary, attached_at, role, status, version (ipv4 or ipv6), kind, and the ip_service_id of the floating IP it belongs to. role is standalone for a single address, host for an address from a subnet and routed for the instance's IPv6 /64, whose address is the network and prefix_len is 64. kind is routed for the /64, block for a subnet or one of its hosts and standalone for anything else.

POST /api/v1/client/vps/{uuid}/ipv6 gives an instance with no IPv6 its /64. It takes no body:

curl -X POST https://api.coritan.com/api/v1/client/vps/$INSTANCE_UUID/ipv6 \
  -H "Authorization: Bearer $CORITAN_TOKEN"

{"prefix": "2001:db8:1000:5::/64", "address": "2001:db8:1000:5::1", "reboot_required": true}

address is the address the instance uses in the /64. reboot_required is true when this request added the /64: restart the instance from the dashboard or with the API so that it sets the address up. Asking again answers the same /64 with reboot_required set to false. The request answers 409 with This location has no IPv6 yet. or This location has no IPv6 left to give out. Contact support. when there is no /64 to give, and 409 while the instance is migrating. An instance that is not yours answers 404, and asking too often answers 429 with a Retry-After header. Any other failure answers 502 with We could not add IPv6 to this instance. Try again in a moment., and the instance keeps no /64 from that request. GET /api/v1/client/vps/{uuid} and GET /api/v1/client/vps show ipv6_address and ipv6_prefix for each instance, both null until it has IPv6.

GET /api/v1/client/vps/{uuid}/ptr returns the reverse DNS of every attached address as items. Each item has the address, is_primary and hostname, which is null when the address has none. The /64 is listed as the address the instance uses in it.

PATCH /api/v1/client/vps/{uuid}/ptr sets the reverse DNS of one address. Send hostname, and address to choose an address other than the primary one. For IPv6, address can be any address in the instance's /64:

curl -X PATCH https://api.coritan.com/api/v1/client/vps/$INSTANCE_UUID/ptr \
  -H "Authorization: Bearer $CORITAN_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"hostname": "mail.example.com", "address": "203.0.113.10"}'

It answers with the address and its new hostname. A name that is not a full domain name answers 422 with a message that starts PTR hostname. An instance with no address answers 404 with This instance has no address to name, and an address that is not on the instance answers 404 with That address is not attached to this instance. The /64 keeps up to 256 names. A name for one more of its addresses answers 409 with This /64 already has 256 PTR records, the most it can keep. Set a new hostname on one of its addresses instead.

POST /api/v1/client/vps/{uuid}/name names the instance. Send the full hostname, from 3 to 253 characters. set_ptr is true when left out. Send set_hostname as true to make the name's first part the instance's hostname, as PATCH /api/v1/client/vps/{uuid}/hostname does (Rename and tag an instance). When that part breaks the hostname rules, the request answers 422 with a detail that starts The guest hostname is the first part of the name., and it saves nothing.

curl -X POST https://api.coritan.com/api/v1/client/vps/$INSTANCE_UUID/name \
  -H "Authorization: Bearer $CORITAN_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"hostname": "vm.example.com", "set_ptr": true}'

{
  "hostname": "vm.example.com",
  "zone": "example.com",
  "records": [{"type": "A", "content": "203.0.113.10"}],
  "ptr": {
    "id": 9,
    "inventory_id": 41,
    "hostname": "vm.example.com",
    "address": "203.0.113.10",
    "version": "ipv4",
    "service_id": 118,
    "created_at": "2026-09-25T10:00:00",
    "updated_at": "2026-09-25T10:00:00"
  },
  "guest_hostname": null
}

records lists only the records the request created. ptr is the primary address's reverse DNS record, or null when you send "set_ptr": false. guest_hostname is the hostname the instance received, such as vm, or null when you left set_hostname out. A name outside your zones answers 403, an instance with no address answers 409 with This instance has no address yet, and a name that holds a CNAME answers 409.

The Cloud Compute API reference lists every field.