Skip to content

[LB] Update dns-records.mdx #22658

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

[LB] Update dns-records.mdx #22658

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions src/content/docs/load-balancing/load-balancers/dns-records.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
Loading