From d076990421b8701bc00c11b07b4e77ae6f68c05e Mon Sep 17 00:00:00 2001 From: Nic <123965403+ngayerie@users.noreply.github.com> Date: Wed, 13 May 2026 23:42:32 +0200 Subject: [PATCH] Update reference to Static IP prefixes in Apex Proxying documentation --- .../start/advanced-settings/apex-proxying/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/apex-proxying/index.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/apex-proxying/index.mdx index a85519119701135..a2109e41e655525 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/apex-proxying/index.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/apex-proxying/index.mdx @@ -26,7 +26,7 @@ In a normal Cloudflare for SaaS [setup](/cloudflare-for-platforms/cloudflare-for However, most DNS providers do not allow `CNAME` records at the zone's root[^1]. This means that your customers have to use a subdomain as a vanity domain (`shop.example.com`) instead of their domain apex (`example.com`). -This limitation does not apply with apex proxying. Cloudflare assigns a set of IP prefixes - cost associated, reach out to your account team - to your account (or uses your own if you have [BYOIP](/byoip/)). This means that customers can create a standard `A` record to route traffic to your domain, which can support the domain apex. +This limitation does not apply with apex proxying. Cloudflare assigns a set of [Static IP prefixes](/byoip/concepts/static-ips/) - cost associated, reach out to your account team - to your account (or uses your own if you have [BYOIP](/byoip/)). This means that customers can create a standard `A` record to route traffic to your domain, which can support the domain apex. [^1]: Cloudflare offers this functionality through [CNAME flattening](/dns/cname-flattening/).