Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DNS] The max number of linked peers per zone #19092

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -85,6 +85,10 @@ To create a peer DNS server using the API, send a [POST](/api/resources/dns/subr

If you previously [created a peer DNS server](#2-create-peer-dns-server-optional), you should link it to your primary zone.

:::note
<Render file="linked-peers-limit" />
:::

<Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">

To link a primary zone to a peer using the dashboard:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -81,6 +81,9 @@ To create a secondary zone using the dashboard:
Cloudflare will not use the REFRESH value inside the SOA record that is served by your primary provider. Instead the value of zone refresh configured for your secondary zone on Cloudflare will be used to determine the interval after which the SOA serial of the primary zone will be checked for changes.
:::
7. Select the peer server you [previously created](#2-create-peer-server). If needed, you can link more than one peer server to a zone.
:::note
<Render file="linked-peers-limit" />
:::
8. Click **Continue**.
9. Review the list of transferred records and click **Continue**.
:::note
Expand Down
4 changes: 4 additions & 0 deletions src/content/docs/dns/zone-setups/zone-transfers/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,8 @@ head:

---

import { Render } from "~/components";

To increase availability and fault tolerance, you can use one or more DNS provider(s) alongside Cloudflare in case one provider becomes unavailable (known as a [peer DNS server](#peer-dns-server)). Your providers will then transfer DNS records between themselves using authoritative ([AXFR](https://datatracker.ietf.org/doc/html/rfc5936)) or incremental ([IXFR](https://datatracker.ietf.org/doc/html/rfc1995)) zone transfers.

With AXFR, the entire zone will be transferred from the primary to the secondary provider, even if only one record changes. With IXFR, only the changes will be transferred. Cloudflare supports both protocols.
Expand All @@ -22,6 +24,8 @@ With zone transfers, you have two configuration options:

Peer DNS servers can be used as primary and secondary external DNS servers. The same peer can be linked to multiple primary and secondary zones. Each peer can be associated with only one Transaction Signature (TSIG).

<Render file="linked-peers-limit" />

You can manage peers via the [API](/api/resources/dns/subresources/zone_transfers/subresources/peers/methods/list/) or the dashboard by going to **Manage Account** > **Configurations** > **DNS Zone Transfers**.

Depending on the usage of the peer, the fields are interpreted in a different way:
Expand Down
6 changes: 6 additions & 0 deletions src/content/partials/dns/linked-peers-limit.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
---
{}

---

The maximum number of linked peers per zone is 30.
Loading