Dashboard
Dashboard is the operational starting point for deployment mode, DNS totals, node health, recent activity, and the shortcuts most often needed during support work.
Where to find it: SDM sidebar > Dashboard.
Available to: All authenticated roles. Cluster creation, joining, and local-node removal require root authority.
What this page does
Use Dashboard to decide where to investigate. It summarizes rather than replaces the detailed modules. In standalone state, root also receives the guarded Create cluster and Join cluster workflows; an existing cluster shows identity, join material, topology shortcuts, and local detach controls.
Before you start
Refresh the page and read the deployment label before acting. For topology work, confirm a current backup, a maintenance window, reachable addresses, and secure custody of the join key.
Cluster onboarding fields
| Workflow | Required fields | Effect |
|---|---|---|
| Create | Cluster name, server label, local server IP, and the acknowledgement that existing DNS setup will be replaced. | Creates a pre-operation backup, initializes cluster identity, and registers this node as the first member. |
| Join | Server label, local server IP, cluster join key, one or more seed hostnames/IPs, and the same replacement acknowledgement. | Creates a backup, contacts an existing member, joins the topology, and hydrates cluster state. |
| Remove this node | The exact local IP confirmation when requested. | Hard-detaches the local server and returns it to standalone state. |
Seed entries accept a hostname, IP address, or the complete private peer address supplied by the cluster owner. That transport is for node onboarding and is not part of the customer API.
Controls and fields
| Control, Field, Or Section | What It Does | What It Affects | Recommended Usage |
|---|---|---|---|
| Refresh | Reloads dashboard status cards, cluster state, DNS summaries, and recent activity. | Refreshes what the operator sees; it does not change DNS data or cluster configuration. | Use it before investigating an incident so you are not acting on stale health data. |
| Create new cluster | Opens the workflow that initializes this server as a new SDM DNS cluster. | Creates cluster identity, join material, local node registration, and replaces standalone DNS setup after the acknowledgement is accepted. | Use only during initial deployment or controlled reinitialization. Confirm backups and maintenance window first. |
| Cluster name | Friendly name for the new DNS cluster, such as a region, datacenter, or customer environment label. | Appears in cluster identity and makes audit/support conversations easier to follow. | Use a stable business label that will still make sense when additional nodes are added. |
| Server label | Human-readable name for the local node. | Displayed in cluster and monitor views to identify this node. | Use a label that describes the node role or location, not a temporary hostname. |
| Server IP | Selects the local address used for cluster communication. | Controls how peers contact this node for cluster operations. | Choose an address reachable by every intended cluster peer before creating or joining. |
| Replacement acknowledgement | Confirms that existing DNS setup on the server may be replaced and that a backup should be created first. | Prevents accidental destructive onboarding. | Do not tick it unless this server is intentionally being converted into the new cluster role. |
| Join existing cluster | Opens the workflow that attaches this server to an existing SDM cluster. | Uses a join key and seed nodes to register this server and synchronize cluster configuration. | Use when adding capacity or replacing a node. Confirm seed reachability and join key freshness. |
| Cluster join key | Secret material generated by the existing cluster and required to authorize a joining node. | Allows the node to authenticate the join operation. | Treat it as sensitive. Rotate or regenerate if it was shared outside the approved deployment flow. |
| Seed node(s) | One or more existing cluster nodes by hostname, IP, or full cluster URL. | Gives the joining node an initial peer to contact. | Enter multiple reachable nodes when possible to avoid a single unavailable seed blocking onboarding. |
| Copy join key | Copies the current cluster join key to the clipboard. | Does not change the key; only prepares it for onboarding another node. | Copy only into secure deployment notes or directly into the join workflow. |
| Open nodes | Navigates to the Cluster Nodes inventory. | Lets the operator inspect membership, health, last-seen data, and removal controls. | Use after create or join to verify the new topology. |
| Backups | Navigates to Backup and Restore. | Lets the operator review restore points before or after cluster changes. | Check backups before disruptive create, join, remove, update, or restore operations. |
| Remove this node | Detaches the local server from the current cluster when the backend reports it is safe. | Changes cluster topology and may require the node to create or join again before participating. | Use only when retiring or rebuilding the local node. |
| Zone manager / Open zones | Navigates to the DNS zone inventory. | Moves the operator from summary cards into zone-level actions. | Use it when dashboard metrics show a DNS-specific issue or customer request. |
| Version, License, Monitor, Logs shortcuts | Open the related administrative module directly from dashboard signal cards. | Does not perform the action itself; it routes the user to the page where action details and confirmations exist. | Use the shortcut that matches the warning card instead of searching manually. |
How to read the result
| Status Or Message | Meaning | What To Check |
|---|---|---|
| Healthy / OK | The dashboard has not detected an immediate problem for that signal. | Still review detailed pages during planned work; healthy summary does not replace full verification. |
| Warning / Degraded / Partial | At least one service, cluster peer, certificate, resource, or sync signal needs attention. | Open the related module from the card and inspect the detailed status. |
| Standalone | The server is not operating as a multi-node cluster member. | Use create or join only if this is intentional onboarding work. |
| Replicated | The server is part of a cluster-oriented DNS deployment. | Verify Cluster Nodes and Monitor when adding or removing peers. |
Safety notes
- Create and join cluster actions are disruptive because they can replace local DNS setup. Use them only during controlled onboarding.
- Remove this node should be treated as a cluster topology change, not as a simple UI cleanup.
How to use it
- Select Refresh and identify healthy, warning, standalone, or clustered state.
- Open the shortcut that owns the signal: zones, monitor, nodes, backup, logs, version, or license.
- For create/join, verify the backup and connectivity, complete every field, then accept the replacement acknowledgement only when conversion is intentional.
- After topology work, open Cluster Nodes and Monitor.
- For routine work, use dashboard totals as a lead and verify the underlying page.
Result and next check
You know whether the node is standalone or clustered and which subsystem needs attention. A successful create/join must appear in Cluster Nodes and health checks; a successful detach must show standalone state.
Theme color