Cluster and Monitoring

Cluster and Monitoring covers deployment topology, replicated settings, node membership, and the checks that warn or recover when a service or resource drifts.

Where to find it: Documentation > DNS Manager > Cluster and Monitoring.

Available to: root for the cluster settings, node, and monitor pages.

What this page does

These pages answer three different questions: which settings belong to the deployment, which servers are members, and whether the services/resources on those servers are healthy. Keeping those questions separate makes failures much easier to locate.

Before you start

Confirm current topology and backup state. Know which values are cluster-wide and which remain local to a node. Peer communication uses a protected private channel and is not an external automation API.

Section map

• Cluster Settings controls replicated timezone, resolver, zone defaults, logging/audit policy, 2FA/IP access, and rate limiting.
• Cluster Nodes shows membership, registry/health, versions, uptime, DNS totals, probes, and removal.
• Monitor configures checks, thresholds, notifications, and optional service actions.

How to use it

1. Read Dashboard and Cluster Nodes before changing topology.
2. Use Cluster Settings only for values intended to follow the deployment.
3. Keep node-specific hostname, interfaces, TLS, SSH, and OS update controls in Local Settings.
4. Configure Monitor thresholds and recipients.
5. After a change, probe nodes and review health rather than relying on the save message alone.

Result and next check

Topology, replicated policy, and health checks agree. If one node differs only in a local setting, correct that node; if a cluster setting differs, investigate synchronization instead of editing every node independently.