diff --git a/src/content/docs/load-balancing/load-balancers/dns-records.mdx b/src/content/docs/load-balancing/load-balancers/dns-records.mdx
index 2acb51acde41fc..0611949f2aa0e8 100644
--- a/src/content/docs/load-balancing/load-balancers/dns-records.mdx
+++ b/src/content/docs/load-balancing/load-balancers/dns-records.mdx
@@ -40,12 +40,17 @@ For hostnames with existing DNS records, the LB record takes precedence when it
   * **Outcome**: LB record takes precedence because it is as specific as the DNS record.
 
 :::note
-
-
 This behavior only applies to [supported records](#supported-records) (determined by your plan type).
+:::
 
+If the DNS record points to a [SaaS provider](/cloudflare-for-platforms/cloudflare-for-saas/) and an active [custom hostname](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/) exists, the custom hostname will take precedence over the Load Balancing record:
 
-:::
+* **Scenario 4**:
+
+  * **CNAME**: `x.example.com` with target to a Cloudflare for SaaS provider
+  * **LB record**: `x.example.com`
+  * **Active custom hostname on the SaaS provider side**: `x.example.com`
+  * **Outcome**: Custom hostname takes precedence.
 
 ## Disabling a load balancer