DirectAdmin Multi-Server Setup can push DNS zones between configured DirectAdmin servers. It is a DNS distribution mechanism, not automatic replication of all website files, databases or mail content. Design the direction of synchronization and ownership before linking production servers.
IN THIS ARTICLE
Information to have ready
Use authorized administrators for both supported servers and confirm their network, TLS and license requirements. Back up existing zones and identify duplicate domain names. Choose which server owns each zone and which servers will answer authoritative queries.
01 Plan a DirectAdmin multi-server DNS setup
- On the source server, open administrator Multi-Server Setup and add the intended receiving server using its supported connection details.
- Create a restricted remote login key with only the commands and source-IP access needed for the documented DNS synchronization workflow. Protect the key and verify the remote server identity.
- Enable the required zone-transfer and domain-check options deliberately. A one-way link pushes source zones to the receiver; a reverse link is a separate decision, not a requirement to enable every synchronization feature.
- Test the connection and a controlled test-zone change. Compare records and serials on all intended authoritative servers. Review queue or retry behaviour for temporary remote failures.
- Only after synchronization works, configure registrar delegation and necessary glue to the intended nameservers. For DNSSEC, preserve the signing-server and signed-zone distribution design.
How do I check DNS synchronization between servers?
Query each authoritative server directly and confirm consistent answers. Test a change and a temporary unavailable-receiver scenario in a controlled environment so monitoring can detect stale zones. Document ownership and credential rotation.
Troubleshoot unexpected results
If a domain check blocks creation during a migration, review the documented migration procedure before relaxing it. Do not disable protections globally to hide duplicate ownership. A successful connection test does not prove every existing zone has been synchronized, and DNS clustering does not provide a current backup of website data.