DNS Cluster

DNS Cluster connects SHM to authorized Synconix DNS cluster nodes and tracks the work used to propagate managed zones beyond the local server.

Where to find it: Open the Server menu and choose DNS Cluster. Conditional items appear only when their service is installed and available.

Available to: Root only.

What this page does

Use it to enable or disable cluster synchronization, configure the seed node and API credentials, discover nodes, test connectivity, synchronize zones, and inspect or retry queued DNS work.

Before you start

This page is root-only. Confirm the remote cluster identity, API scope, source-address policy, TLS trust, authoritative DNS design, and a rollback plan before enabling synchronization. Never place cluster credentials in screenshots or public documentation.

Cluster workflow

1. SHM reads the saved seed and cluster policy.
2. A connectivity test proves the credential and remote API are reachable.
3. Node discovery refreshes the cluster view.
4. Zone changes enqueue supported synchronization jobs.
5. The queue records pending, successful, failed, and retried work.

Queue

Inspect the job kind, zone, destination, attempts, timestamps, and latest error before retrying or deleting a queue item. Retrying an authorization or data conflict without fixing its cause only produces a newer timestamp for the same problem.

DNS boundary

Cluster synchronization updates the configured DNS platform. It does not change registrar nameserver delegation, replace public TTL expiry, or prove that a resolver is querying the intended authoritative nodes.

How to use it

1. Save the minimum required cluster settings.
2. Run the connection test.
3. Discover and verify the expected nodes.
4. Synchronize one controlled test zone.
5. Follow its queue job to success and query every intended authoritative node.
6. Expand use only after the test result is consistent.

Result and next check

Configured zone changes reach the intended cluster nodes, queue jobs reach a final successful state, and authoritative queries return consistent records. External delegation and cached resolver results must still be verified separately.