diff --git a/src/content/changelog/dns/2026-06-10-account-level-record-quota.mdx b/src/content/changelog/dns/2026-06-10-account-level-record-quota.mdx
new file mode 100644
index 00000000000..a13a8919155
--- /dev/null
+++ b/src/content/changelog/dns/2026-06-10-account-level-record-quota.mdx
@@ -0,0 +1,11 @@
+---
+title: Account-level DNS records quota
+description: Enterprise accounts now have a single DNS records quota across all of their zones.
+date: 2026-06-10
+---
+
+Cloudflare now enforces DNS records quotas at the account level for Enterprise accounts. Instead of a per-zone limit, these accounts have a quota on the total number of records across all of their zones, letting you distribute records across your zones however you like — regardless of each zone's plan. Public and internal zones are counted separately, each with a default quota of 1,000,000 records.
+
+Accounts without an account-level quota are unaffected: existing per-zone quotas behave exactly as before.
+
+For more details, refer to [DNS records quota](/dns/manage-dns-records/#dns-records-quota).
diff --git a/src/content/docs/dns/faq.mdx b/src/content/docs/dns/faq.mdx
index cb2d29d2d05..dbe355f598c 100644
--- a/src/content/docs/dns/faq.mdx
+++ b/src/content/docs/dns/faq.mdx
@@ -109,7 +109,7 @@ Free zones created before 2024-09-01 00:00:00 UTC have an increased limit of 1,0
If you are an Enterprise customer and require more DNS records, contact your account team. Cloudflare can support millions of DNS records on a single zone.
:::
-DNS records that other Cloudflare services create on your behalf — for example, the `TXT` and `MX` records added by [Email Routing](/email-routing/) — also count toward this limit. To avoid disrupting those services, they are enforced against your record limit with a small buffer, so a zone may occasionally hold slightly more records than its limit would otherwise allow.
+DNS records that other Cloudflare services create on your behalf — for example, the `TXT` and `MX` records added by [Email Routing](/email-service/) — also count toward this limit. To avoid disrupting those services, they are enforced against your record limit with a small buffer, so a zone may occasionally hold slightly more records than its limit would otherwise allow.
To create new records yourself through the dashboard or API, your zone must still be within its record limit.
diff --git a/src/content/docs/dns/manage-dns-records/index.mdx b/src/content/docs/dns/manage-dns-records/index.mdx
index 3f37277fb09..dbc611da8cc 100644
--- a/src/content/docs/dns/manage-dns-records/index.mdx
+++ b/src/content/docs/dns/manage-dns-records/index.mdx
@@ -48,7 +48,13 @@ Also, as this record is zone.
+Cloudflare limits the number of DNS records you can create. Depending on your plan, this limit is enforced either per zone or per account — not both.
+
+DNS records that other Cloudflare services create on your behalf also count toward your quota.
+
+### Per-zone quota
+
+By default, there is a limit to the number of records you can create on a single zone.
- Free zones created before `2024-09-01 00:00:00 UTC`: 1,000
- Free zones created on or after `2024-09-01 00:00:00 UTC`: 200
@@ -56,9 +62,19 @@ There is a limit to the number of records you can create on a single