Skip to content

DNS Cluster

Synchronize eligible local PowerDNS zones to connected DNSOnly targets.

1Overview

DNS Cluster delivers panel-owned zones from local PowerDNS through the protected BigCloudy gateway to configured WHM DNSOnly targets. It does not change a domain registrar or unrelated external zone.

DNS Cluster in the administrator panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.
DNS Cluster overview showing local PowerDNS, remote WHM synchronization, connection status, and synchronization results.

DNS Cluster in the administrator panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.

2Before you begin

Administrator actions can affect multiple customer accounts and server services. This is an advanced task; schedule it carefully and keep a rollback path.

3Step-by-step workflow

Open DNS Cluster, verify Synchronization running and the target status, then use Sync domains now for all eligible domains or enter one domain and choose Sync selected domain. Review the result and error counters after the job completes.

  1. Open DNS Cluster and distinguish local DNS service health from the remote WHM nameserver connections.
  2. For each target, enter the DNSOnly HTTPS URL, API username, token, and connection role.
  3. Select Include in synchronization only for targets that should receive these zones.
  4. Configure exactly one included primary when the page requires a primary synchronization coordinator.
  5. Use Test connection and review its result before enabling synchronization.
  6. Use Save draft to retain settings, or Save and synchronize to verify and apply the selected configuration.
  7. For a later update, use Sync selected domain or the all-domains action and wait for its result.
  8. Review each target and any failed domain, then confirm the expected zone on the remote DNS server.

4Practical example

Example: a blank token field can mean the token is already saved securely. Leave it blank to retain the saved credential when the form says so; enter a replacement if the endpoint or API identity changes.

5Verify the result

Validate the outcome from the affected account or an independent client connection, not only from the administrator screen.

  1. Confirm the success, pending, and error counters update.
  2. Check the target DNSOnly server contains the expected zone and records.

6Common problems and what to check

SOURCE_ZONE_MISSING: confirm the domain has a local panel-owned DNS zone before synchronization.

Authentication or TLS fails: test the saved target, its certificate, token permissions, and network access.

A zone is not reaching a server: confirm that target is included and review the worker result rather than repeatedly saving the form.

7Security, impact, and rollback

Only synchronize zones owned by the panel. Resolve missing local zones, ownership conflicts, or target connection errors before repeatedly queuing jobs.

Related guides

SSL/TLS certificatesIssue, inspect, renew, and remove website certificates.DNS zonesManage local DNS zones and records for hosted domains.See all guides in Administrator panel

Still need a hand?

Get help with your plan, website, or hosting through your client area.

Open client area