The panel can give every server a full name under your domain, keep its A and AAAA records at Cloudflare, and set the reverse DNS (PTR) name of each public address through your provider's API. Each part is optional and works without the others.
All three are set on System › Settings (the General tab), in the panels Domain, Cloudflare and Reverse DNS.
Before you start#
Every Cloudflare and provider call runs on the panel's own dns queue, never in a page request, so a slow provider cannot hold up node work. The panel installer sets up its worker. Check it runs:
systemctl status vmstack-worker@dns-1
If the worker is stopped, DNS records and reverse names stay Waiting for ever.
Server names#
The Hostname (optional) field of the create form is optional. Left empty, the panel generates vps- followed by six lower-case letters and digits, for example vps-k3x9q2, avoiding every name and full name already used.
A full name is unique across the panel, whatever its case ("That name is already used.").
The panel's domain#
To give servers a full name under your domain:
- Go to System › Settings.
- In the Domain panel, fill in Domain of servers' names, for example
cloud.example.com. - Optionally change Reserved names (see below).
- Click Save domain.
From then on a server named web-01, typed or generated, is created as web-01.cloud.example.com: the server gets web-01 as its hostname and the full name in /etc/hosts. A name typed with a dot (mail.example.org) is taken as the full name and the domain is not added.
Existing servers keep their names. A reinstall with a new name gets the domain in the same way.
Reserved names#
Under the panel's domain some first labels are refused, so a customer cannot take www or mail of your own domain. The default list is: www, mail, smtp, imap, pop, pop3, mx, ns, ns1, ns2, ftp, webmail, panel, api, admin, autodiscover, autoconfig, cpanel, whm, vpn, and @ (the domain itself).
An administrator can still use one: tick Allow a reserved name of the panel's domain (www, mail…) on the create form or in Reinstall.
A and AAAA records through Cloudflare#
With the domain and a Cloudflare zone set, each server under the domain gets:
| Record | Points to |
|---|---|
| A | the server's main IPv4 address |
| AAAA | the server's first IPv6 address |
Records are proxied off, with automatic TTL, and carry the comment vmstack:<server id>. They are made after the server is created, changed when its addresses change or a reinstall renames it, and deleted with the server. A server behind NAT gets no A record. A typed full name outside the panel's domain gets no record.
To connect Cloudflare:
- At Cloudflare, create an API token with the permission Zone · DNS · Edit, limited to the zone of your domain.
- Copy the zone's ID from its overview page.
- In System › Settings, panel Cloudflare, fill in Zone ID and API token, then click Save Cloudflare.
- Click Check. The panel reads the zone's name through the API and shows the result.
The token is stored encrypted and never shown again; the panel shows "Token saved (ends …4f2a)" with Remove. Removing it leaves the records at Cloudflare as they are.
Records the panel does not own#
The panel only changes or deletes records whose comment is its own for that server. Before making a record it lists the name's records of every type; if any belongs to someone else (your own www, another server's record), it makes none. Administrators then read on the server page:
DNS record not created yet: The name is already used in the domain's DNS
Failures and retries#
A failed call never holds up creating or deleting a server. It is tried again after 1 minute, 5 minutes, 30 minutes, then every 6 hours. Administrators see "DNS record not created yet:
Reverse DNS#
Reverse DNS is set per IP block. Each block either uses a provider account, which the panel calls to set the PTR names, or is Manual, where the panel records the wanted names and lists them for you to set at the provider.
Supported providers#
| Provider | Credentials | Options | Notes |
|---|---|---|---|
| OVHcloud | Application key, Application secret, Consumer key | Endpoint: Europe, Canada, United States | The forward record must resolve first. |
| Leaseweb | API key | An IPv4 name cannot be taken off; it is left. | |
| PidginHost | API token | No way to take a name off. | |
| Cherry Servers | API token | Project id (required) | Taking a name off writes the default name back. |
| Contabo | Client id, Client secret, API user, API password | An IPv4 name cannot be taken off; it is left. | |
| Scaleway | Secret key | Region (Paris, Amsterdam, Warsaw, Milan), Project id (optional) | The forward record must resolve first. |
| ReliableSite | API key | Allow the panel's public IP in ReliableSite's control panel; no way to take a name off. | |
| Own name servers (PowerDNS) | API key | API URL, Server id (default localhost), Name servers of new zones |
The panel creates the reverse zone the first time. |
Note: The provider integrations were built from each provider's API documentation and tested against recorded request and answer shapes. If a provider answers differently, the address shows Failed with the provider's own words; please report it.
For PowerDNS, an IPv4 PTR goes into the reverse zone of the /24 the address is in. RFC 2317 delegation of smaller blocks is not handled. The API URL must be http or https.
The panel never sends a DELETE for an IP to Cherry Servers or Scaleway, because there it releases the IP from your account.
Add a provider account#
- Go to System › Settings, panel Reverse DNS.
- Under Add an account, choose the Provider, give the account a Name (for example "OVH main") and fill in its credentials and options.
- Click Add account.
- Click Check next to the account. It makes one read-only call and shows the answer.
Credentials are stored encrypted and shown only by their last four characters. Removing an account turns its blocks to Manual; the names already set at the provider stay.
Choose the account for a block#
- Go to Infrastructure › IP pools and open the block.
- Click Edit block.
- Under Additional settings, choose the account in Reverse DNS, or leave it Manual.
- Click Save changes.
The same field is on the Add IP block form, so a new block can get its account straight away.
Choosing another account asks it to set the names the block's addresses already have. The old account's names are not taken off. See IP pools for the rest of the block form.
When names are set#
- Server created: each public address (IPv4 not behind NAT, single IPv6 addresses) gets the server's full name.
- Server reinstalled with a new name: names that still equal the old name follow the new one.
- Address leaves the server: its name is taken off. Where the provider cannot take it off, the address gets a generic name under the panel's domain, such as
198-51-100-10.cloud.example.com. Without a domain, or in a Manual block, the old name is listed for an administrator to remove by hand.
A clear never takes off a name that the address got since, or that belongs to another server.
Edit a name#
| Who | Where |
|---|---|
| The server's owner, the owner's reseller, administrators | Servers › Networking, Edit on the address; or the server's Network tab, Edit under the address |
| Administrators | the block's page in Infrastructure › IP pools, Reverse name on the address |
The name must be a valid host name of up to 253 characters. Customers and resellers may change a name at most 3 times per address and 5 times in all per 10 minutes; administrators are not limited.
To restrict what customers may set, choose Customers may set in the Reverse DNS panel:
| Choice | Effect |
|---|---|
| Any name | the default |
| Only names under the panel's domain | the name must end in the panel's domain |
| Only names that resolve to the address | the panel looks up the name's A or AAAA record before setting it |
States#
| State | Meaning |
|---|---|
| Applied | the provider accepted the name |
| Waiting | queued, or waiting for the forward record (OVHcloud, Scaleway) |
| Failed: … | the provider refused; administrators see the provider's message, customers "The provider did not take it yet. It is tried again." |
| Manual: set it with your provider | the block has no account |
Failures are retried on the same schedule as Cloudflare records and given up after 8 attempts. On the block page, Retry name starts again.
For OVHcloud and Scaleway the forward record must resolve before the reverse name is accepted. For a name under the panel's domain the panel waits until its own A or AAAA record is applied; for other names it asks at once and shows the provider's answer.
Names to set by hand#
When names wait for you (Manual blocks, or old names that could not be taken off), the Reverse DNS panel says how many and lists each address with "Set
Check the result#
After a name shows Applied, check it from any machine once the provider's DNS has refreshed:
dig -x 198.51.100.10 +short
dig A web-01.cloud.example.com +short
The audit log records ip_address.rdns_changed (old name, new name, who), dns.record_created, dns.record_updated, dns.record_deleted, dns.record_failed and the dns_provider.* entries.
If records or names stay Waiting or Failed, see Networking troubleshooting.