diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/setup.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/setup.mdx
index 1678c3f3c74359..3278794858803d 100644
--- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/setup.mdx
+++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/setup.mdx
@@ -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:
diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup.mdx
index 7dac1f43fe7ad8..a30e2261dbfe67 100644
--- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup.mdx
+++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup.mdx
@@ -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
diff --git a/src/content/docs/dns/zone-setups/zone-transfers/index.mdx b/src/content/docs/dns/zone-setups/zone-transfers/index.mdx
index 993b6c38a307b1..5d5e3841bafa81 100644
--- a/src/content/docs/dns/zone-setups/zone-transfers/index.mdx
+++ b/src/content/docs/dns/zone-setups/zone-transfers/index.mdx
@@ -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.
@@ -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:
diff --git a/src/content/partials/dns/linked-peers-limit.mdx b/src/content/partials/dns/linked-peers-limit.mdx
new file mode 100644
index 00000000000000..07cf4abcd9e4cc
--- /dev/null
+++ b/src/content/partials/dns/linked-peers-limit.mdx
@@ -0,0 +1,6 @@
+---
+{}
+
+---
+
+The maximum number of linked peers per zone is 30.