Your package and DNS provider must allow secondary zones. The primary server must permit zone transfers to the intended secondary, and any required transfer authentication must be configured correctly. You also need the primary server's reachable IP addresses and permission to publish the zone on both services.

Ask the operator for the correct transfer addresses and supported authentication procedure. Do not enable unrestricted zone transfers to the entire internet just to make a setup test pass.

1. Open the account DNS zones view and start setup for an eligible domain.
2. Choose the secondary-zone option when it is offered.
3. Enter the primary or master IP addresses in the requested format.
4. Complete any ownership verification needed for the domain.
5. Submit the setup and wait for the transfer task to complete.
6. Inspect the secondary's records and its SOA serial, and compare them with the primary.

Update the records at the primary server. A secondary follows the primary's data; it is not normally a separate place to make unrelated record edits. After a change, verify that the secondary receives the newer zone and answers consistently. The transfer mechanism and schedule determine how quickly this happens.

Changing the list of public nameservers at the registrar is a separate action. Add only authoritative servers that are ready to answer for the zone. For DNSSEC, signing and transfer compatibility need a coordinated design; do not assume a second provider automatically shares the primary's signing configuration.

A package that uses API replication across selected providers may not offer secondary-zone creation. Those are different synchronisation methods. If a transfer fails, check the primary address, transfer permissions, firewall reachability, zone serial and authentication with the server operator. Include the domain and transfer error when contacting support. Do not recreate the zone as an unrelated primary unless you intentionally want to maintain separate copies yourself.

• Add a domain registered elsewhere to your DNS Manager
• Check DNS propagation and find the source of an old answer
• Synchronize a DNS package across multiple servers and select its master
• Configure secondary DNS with an authorised transfer source

• PowerDNS: Zones API