The article offers the steps to set up a DirectAdmin (DA) DNS cluster. Bobcares, as a part of our DirectAdmin Support Services offers solutions to every query that comes our way.

How to Set Up a DirectAdmin DNS Cluster?

We need at least two servers are required for the creation and setup of an external DirectAdmin (DA) DNS cluster: one for the primary DNS and another for the secondary DNS. To set up the external DA DNS cluster, take the following steps:

1. Go to “DNS Administration” under “Advanced Features” after logging into the primary server’s DirectAdmin dashboard.

2. Click the “Add DNS Cluster” link under the “External DNS” section.

3. Then, complete the following fields: cluster name, cluster username and password, secondary DNS server IP address or hostname, and transfer method. Select the right transmission mechanism according to the network and security requirements.

4. To set up the cluster, click “Save”. When the secondary server connection is tested, DirectAdmin will report any faults or warnings to user.

5. Go to “List DNS Clusters” in the “External DNS” section after the cluster has been created. Click “Edit” after selecting the cluster we just created.

6. We can select which zones to move to the backup server in the cluster settings. Additionally, we can also adjust the sync frequency and activate or disable zone syncing.

7. Proceed to the secondary server after saving the cluster settings. Go to “DNS Administration” after logging onto the DirectAdmin dashboard. Select “Add DNS Cluster” and provide the primary server’s details.

8. The secondary server will start synchronizing the zones with the primary server as soon as it is introduced to the cluster. By examining the logs or the DNS cluster status on the DirectAdmin dashboard, we can keep an eye on the progress of the syncing process.

[Want to learn more? Click here to reach us.]

Conclusion

To sum up, setting up and configuring an external DirectAdmin DNS cluster has been handled. Also, test the cluster by modifying the zones on the primary server and confirm that the secondary server receives a replication of those changes.