1. Identify every zone using the package and note which nameservers answer publicly. Export important records and keep a recent zone backup.
2. Add the proposed destination connection to the package if it is not already present. Test credentials and confirm that each zone can be created or bound there under the correct owner.
3. Check compatible record types and provider-specific features. Plan DNSSEC and proxy changes separately. A record copy cannot preserve a signing key or an HTTP proxy setting automatically.
4. Compare the proposed master's records with the current source. Resolve unexplained differences before selecting it as the new source of truth.

Open the package's Servers tab, select the intended Master server and save the configuration. Monitor synchronization and verification for each assigned server. Do not regard the selection control alone as proof that the destination has a complete working zone.

The implementation verifies transitions and retains the old master when a required change fails. Read the resulting status and address the failure. Repeatedly deleting or recreating connections can discard useful evidence and complicate recovery.

If customers will continue using the same authoritative nameserver network, a management-source change may not require registrar action. If the authoritative service is moving, prepare the new network, verify all records and arrange the appropriate nameserver and DNSSEC transition.

Keep the old authorities serving correct records while cached delegation remains in use. Reducing record TTLs can help future record changes, but it does not erase already cached delegation or parent DS records. Check website and mail behaviour through the transition.

After the new arrangement is stable, decide whether the old server should remain a synchronized target or leave the package. Removing it from the package does not delete its remote zones. Delete obsolete zones only after confirming that they have no remaining delegated domains or other consumers.

Record the change, resulting master, authoritative nameservers and backup location. This gives support enough context to distinguish an intentional migration from accidental drift during a later investigation.

• Synchronize a DNS package across multiple servers and select its master
• Configure DNS backups and restore a reviewed record snapshot
• Operate DNSSEC from zone signing through parent DS verification
• Check DNS propagation and find the source of an old answer