How to set up a DNS cluster (secondary DNS on another server)
On this page
With a DNS cluster, another server running this control panel keeps a copy of this server's DNS zones and answers for them. You can then point one nameserver name at each server, so domains keep resolving when one server is down.
Before you start
- You need a second server with this control panel installed, reachable over HTTPS at its hostname with a valid certificate.
- You need the administrator panel of both servers.
Steps
- On the other server's administrator panel, open API Tokens (section Account) and create a token. Copy it.
- On this server, log in to the administrator panel (
https://your-server:2087). - Open Servers (cluster) in the menu (section Server).
- Under Add a server, enter:
- Name — for example
Server 2 - Admin panel address — for example
https://server2.example.net:2087 - API token — the token from step 1
- Name — for example
- Tick DNS cluster: let that server copy and answer for this server's DNS zones.
- Click Add server. The server appears in the list with DNS cluster On.
- Point one of your nameserver names at the other server. For example, change the glue record of
ns2.example.netat your registrar, and theArecord ofns2in your zone, to the other server's IP address198.51.100.20.
What happens next
- The other server copies every zone of this server through signed zone transfers (a key shared only between the two servers).
- Record changes reach it within seconds: this server notifies it after each change.
- New and deleted zones are sent to it automatically.
- On the other server, Servers (cluster) shows the copied zones under Zones this server copies from others.
Start or stop the cluster for a server
Open Servers (cluster), click Manage next to the server, then Start the DNS cluster or Stop the DNS cluster. When you stop it, the other server drops the copies. Move your nameserver name back first.
Good to know
- To copy in both directions, add each server on the other with the box ticked.
- If the other server already hosts a zone with the same domain, it keeps its own and does not copy this one.
- Errors (for example the other server could not be reached) appear under the server's name in the list.
Common questions
Do I edit records on both servers?
No. Edit them only on the server that hosts the zone; the copy follows.
Can the second server be a different DNS product?
No. The cluster works only between servers running this control panel.
Thank you — this helps us improve the article.
Still stuck?
Ask the AI about your exact situation — it answers from this knowledge base — or contact us.
Related articles
- How to set up your server's nameservers (ns1 and ns2)
Make your server answer DNS as ns1 and ns2 of your own domain: set the names, create their address records and register glue records at the registrar.
- How to edit any DNS zone as administrator or reseller
Find, open and edit the DNS zones of customer accounts from the DNS Zones page of the administrator panel, as the server administrator or a reseller.
- How to set up private nameservers for a reseller
Give a reseller branded nameservers such as ns1.their-brand.com, register glue records, and apply the new nameservers to existing customer zones.