> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/network-services/cloud-dns/dcd-how-tos/public-zone/secondary-zone/start-zone-transfer.md).

# Start Zone Transfer

IONOS Cloud DNS: transfer zone records from primary to secondary using the DCD

A zone transfer is a fundamental process for replicating DNS records from a primary DNS server to one or more secondary servers. This process ensures redundancy, enhances fault tolerance, and improves DNS resolution performance across distributed networks.

Creating a zone transfer from a primary to a secondary zone involves configuring authoritative DNS servers to synchronize zone data securely. The primary server maintains the original zone file; the secondary servers obtain and periodically update their copies through the standard [<mark style="color:blue;">AXFR</mark>](https://docs.ionos.com/cloud/support/general-information/glossary-of-terms#authoritative-zone-transfer-axfr) zone transfer protocol.

{% hint style="info" %}
**Prerequisites:**

* Cloud DNS relies on the following Anycast addresses to send DNS notification messages. Ensure you whitelist the following IP addresses:
* **IPv4:** `212.227.123.25`
* **IPv6:** `2001:8d8:fe:53::5cd:25`
* Ensure that port 53 is open for both TCP and UDP connections.
  {% endhint %}

To begin zone transfer, follow these steps:

1\. In the **DCD**, go to **Menu** > **Network Services** > **Cloud DNS** > **Public zones** tab.

2\. Select **Secondary Zones** from the drop-down list.

![Select secondary zones](https://1737632334-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MifAzdGvKLDTtvJP8sm%2Fuploads%2Fgit-blob-a6f5bed26c91646a13e365704c94227106c06849%2Fselect-secondary-zone.png?alt=media)

{% hint style="info" %}
**Info:** The **Public zones** section displays the zones if you have already created them. Select **Show secondary zones** to view secondary zones. This option only appears if you have created secondary zones but have not configured primary zones.
{% endhint %}

![Show secondary zones](https://1737632334-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MifAzdGvKLDTtvJP8sm%2Fuploads%2Fgit-blob-25843a899cf055d1f3c7cdf74ae555eb3f11e29b%2Fshow-secondary-zone.png?alt=media)

3\. Select the zone to initiate the transfer process.

4\. Select **Start zone transfer**.

![Select zone transfer](https://1737632334-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MifAzdGvKLDTtvJP8sm%2Fuploads%2Fgit-blob-44c0c15dc3022dd2476cc92a5eaf5e292390d839%2Fselect-zone-transfer.png?alt=media)

Alternatively, you can begin zone transfer using the **Start zone transfer** option in either the [<mark style="color:blue;">ACTIONS</mark>](/cloud/network-services/cloud-dns/dcd-how-tos/public-zone/secondary-zone/view-secondary-zones.md) column or the [<mark style="color:blue;">Details & Records</mark>](/cloud/network-services/cloud-dns/dcd-how-tos/public-zone/secondary-zone/view-secondary-zone-details.md) window.

5\. Select **Start transfer** in the **Start zone transfer** view to begin the process.

![Confirm zone transfer](https://1737632334-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MifAzdGvKLDTtvJP8sm%2Fuploads%2Fgit-blob-df91ade4d61f90c5ea79daf55e4fc71489e6150e%2Fconfirm-zone-transfer.png?alt=media)

{% hint style="success" %}
**Result:** The zone transfer process has begun.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ionos.com/cloud/network-services/cloud-dns/dcd-how-tos/public-zone/secondary-zone/start-zone-transfer.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
