From 16d103562dc7b20a35a13633487756ff9fdc0c88 Mon Sep 17 00:00:00 2001 From: Angela Costa Date: Tue, 24 Jun 2025 15:10:51 +0100 Subject: [PATCH] Adds scenario to DNS records --- .../docs/load-balancing/load-balancers/dns-records.mdx | 9 +++++++++ 1 file changed, 9 insertions(+) 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 4d7c05c820d3f9..bcb9c73da8ea33 100644 --- a/src/content/docs/load-balancing/load-balancers/dns-records.mdx +++ b/src/content/docs/load-balancing/load-balancers/dns-records.mdx @@ -47,6 +47,15 @@ This behavior only applies to [supported records](#supported-records) (determine ::: +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 When you disable a load balancer, requests to a specific hostname depend on your existing DNS records: