[CF4SaaS] Add warning about same name as zone (#27169)

RebeccaTamachiro · web-flow · commit 06f22c18a690 · 2025-12-19T10:15:17.000Z
* AI-assisted: suggest places and create and apply partial

* Fix missing Render on troubleshooting.mdx

* Use new partial inside get-started-per-hostname partial

* Move caution note higher on create-custom-hostnames.mdx

* AI-assited: move caution wrap from partial into files themselves

* Adjust note to avoid caution in sequence

* Simplify callout content and use explanation on troubleshooting
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/create-custom-hostnames.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/create-custom-hostnames.mdx
@@ -11,6 +11,12 @@ import { Render, TabItem, Tabs } from "~/components";
 
 There are several required steps before a custom hostname can become active. For more details, refer to our [Get started guide](/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/).
 
+:::caution[Zone name restriction]
+
+<Render file="same-name-as-zone" product="cloudflare-for-platforms" />
+
+:::
+
 To create a custom hostname:
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/troubleshooting.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/troubleshooting.mdx
@@ -9,7 +9,7 @@ head:
 
 ---
 
-import { Details } from "~/components";
+import { Details, Render } from "~/components";
 
 ## Rate limits
 
@@ -78,6 +78,16 @@ example.com CAA 0 issuewild "ssl.com"
 
 More details can be found on the [CAA records FAQ](/ssl/edge-certificates/troubleshooting/caa-records/).
 
+***
+
+## Custom hostname matches zone name (403 Forbidden)
+
+<Render file="same-name-as-zone" product="cloudflare-for-platforms" />
+
+This configuration will cause a 403 Forbidden error due to DNS override restrictions applied for security reasons. This limitation also affects Worker Routes making subrequests.
+
+***
+
 ## Older devices have issues connecting
 
 As Let's Encrypt - one of the [certificate authorities (CAs)](/ssl/reference/certificate-authorities/) used by Cloudflare - has announced changes in its [chain of trust](/ssl/concepts/#chain-of-trust), starting September 9, 2024, there may be issues with older devices trying to connect to your custom hostname certificate.
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/worker-as-origin.mdx
@@ -10,6 +10,8 @@ description: Learn how to use a Worker as the fallback origin for your SaaS zone
 
 ---
 
+import { Render } from "~/components";
+
 If you are building your application on [Cloudflare Workers](/workers/), you can use a Worker as the origin for your SaaS zone (also known as your fallback origin).
 
 1. In your SaaS zone, [create and set a fallback origin](/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/#1-create-fallback-origin). Ensure the fallback origin only has an [originless DNS record](/dns/troubleshooting/faq/#what-ip-should-i-use-for-parked-domain--redirect-only--originless-setup):
@@ -33,3 +35,11 @@ If you are building your application on [Cloudflare Workers](/workers/), you can
      * **Worker**: **None**
 
 5. Click **Save**.
+
+---
+
+:::caution[Zone name restriction]
+
+<Render file="same-name-as-zone" product="cloudflare-for-platforms" />
+
+:::
diff --git a/src/content/partials/cloudflare-for-platforms/get-started-per-hostname.mdx b/src/content/partials/cloudflare-for-platforms/get-started-per-hostname.mdx
@@ -16,18 +16,22 @@ Before you create a hostname, you need to plan for:
 
 You must complete both these steps for the hostname to work as expected.
 
-:::caution[Important]
-
+:::note
 
 Depending on which method you select for each of these options, additional steps might be required for you and your customers.
 
-
 :::
 
 ### 2. Create custom hostname
 
 After planning for certification and hostname validation, you can create the custom hostname.
 
+:::caution[Zone name restriction]
+
+<Render file="same-name-as-zone" product="cloudflare-for-platforms" />
+
+:::
+
 To create a custom hostname:
 
 <Tabs> <TabItem label="Dashboard">
diff --git a/src/content/partials/cloudflare-for-platforms/same-name-as-zone.mdx b/src/content/partials/cloudflare-for-platforms/same-name-as-zone.mdx
@@ -0,0 +1,6 @@
+---
+{}
+
+---
+
+Do not configure a custom hostname which matches the zone name. For example, if your SaaS zone is `example.com`, do not create a custom hostname named `example.com`.

-Original file line number
+Diff line change
@@ @@ -0,0 +1,6 @@ @@
 +---
 +{}
++
 +---
++
 +Do not configure a custom hostname which matches the zone name. For example, if your SaaS zone is `example.com`, do not create a custom hostname named `example.com`.