DNS Cluster / DNSOnly
Install, link, and validate an independent DNSOnly node.
DNSOnly is a satellite of the same commercial license as the primary server. It receives a restricted entitlement and cannot be used as a second hosting installation.
1. Install the DNSOnly node
Terminal
cd /home && curl -o latest-dnsonly -L https://securedownloads.fivergames.com/latest-dnsonly && sh latest-dnsonly
2. Link it to the primary license
On the primary serverOpenDNS Cluster / DNSOnlyand generate a single-use linking code.
On DNSOnlyEnter the code on the activation screen. Do not use the commercial key directly.
Complete onboardingSet the node hostname, management domain, and administrator.
Generate the node tokenOn DNSOnly, generate the cluster token and copy it to the primary server.
Add the peerEnter name, public IPv4, HTTPS endpoint, and token. The primary validates the satellite identity, license, and role.
SynchronizeUseSynchronize nowand verify the peer status.
3. Publish independent nameservers
Conceptual example:
| Name | IPv4 |
|---|---|
| ns1.yourdomain.com | Primary server public IP |
| ns2.yourdomain.com | DNSOnly public IP |
At the registrar, also create thechild nameservers/gluewith the same IPs.
4. Validate replication
Terminal
dig @IP-PRIMARY example.com SOA +norecurse +short dig @IP-DNSONLY example.com SOA +norecurse +short dig @IP-PRIMARY example.com DNSKEY +dnssec +norecurse dig @IP-DNSONLY example.com DNSKEY +dnssec +norecurse
The serials must converge. For a real change, create a record on the primary and confirm that it appears on DNSOnly after the transfer.
Cloud firewallIn addition to the VM UFW, some environments require additional inbound rules in the cloud network firewall for 53/TCP, 53/UDP, and 2083/TCP.