Migrating Between DNS Providers #

SynergyCP keeps the authoritative copy of every PTR record in its own database, so you can switch DNS providers without losing anything — for example from a legacy BIND server to PowerDNS v4, or from self-hosted PowerDNS to Cloudflare.

Steps #

Set up the new provider (Setup) and enter its details in Admin > System > Settings > DNS. From this moment, new PTR changes go to the new provider.
Replay every stored record to the new provider by running the bulk sync command on the SynergyCP server:
```
/scp/bin/scp-exec php_s php artisan rdns:sync-to-dns
```
The command streams every PTR record in the database to the currently configured provider, creating zones as needed, and reports successes and failures. It is safe to run repeatedly — records that already exist are simply set to the same value again.
Spot-check a few records against the new DNS server:
```
dig +noall +answer -x <ip> @<new DNS server>
```
Update the nameserver delegation for your IP ranges with your RIR or upstream provider to point at the new DNS server (for Cloudflare, the assigned nameservers — see Nameserver delegation).
Keep the old DNS server running until the delegation change has propagated, then decommission it.

rdns:sync-to-dns is also useful outside migrations — for example to repopulate a provider after restoring it from an old backup, or to heal drift if records were changed on the DNS server directly.