JSOPanel Get started
Help Center › Administrators › Linking servers into a DNS cluster

Linking servers into a DNS cluster

How to share DNS records across multiple JSOPanel servers for nameserver redundancy.

With a single server, that server is the only nameserver answering for your domains, so if it becomes unreachable, the domains it hosts become unreachable too, even if the websites themselves are fine. A DNS cluster links two or more JSOPanel servers so they answer for each other: each server keeps the domains that live on it and holds copies of everybody else's.

Setting up a cluster

  1. On your first server, normally the one that already has your domains on it, click DNS cluster in the sidebar.
  2. Under "Start a cluster", confirm this server's address and click Start a cluster here. This creates the shared key and starts offering this server's domains to whoever joins.
  3. On every other server you want to add, open the same page and use "Join a cluster": enter this server's own address, the address of a server already in the cluster, and the cluster key copied from that server's own DNS cluster page.

Once joined, the Status card on this page shows every server in the cluster and whether each one is currently answering, checked live every time the page loads. The same page shows The cluster key itself, needed by any further server joining, and a Rebuild the list of domains card with a Rebuild now button if a server's own copy of who holds which domain ever needs refreshing by hand.

Important: joining a cluster alone isn't quite the whole setup. The servers also need to trust each other for domain-conflict checking, done once on the Second Server page: go there on this server and on the other one, and trust each other's key, the same step used for keeping a second server in sync. Nothing on the DNS cluster page itself warns you if this step is missing.

Leaving a cluster

A server can be removed from a cluster at any time from the same DNS cluster page, without affecting the domains that remain hosted on it directly.

Tip: a DNS cluster is about nameserver redundancy, having more than one server able to answer for your domains. If you also want visitors automatically sent to whichever of two paired servers is geographically closer, that's a separate feature, near-server steering, and it lives on the Second server page instead. It needs an account to already be copied to that other server, and doesn't require a DNS cluster at all.