Skip to content

[DNS] Proxy status use cases #29789

Merged
RebeccaTamachiro merged 11 commits into
productionfrom
rebecca/dns-proxy-status-use-and-limits
Apr 21, 2026
Merged

[DNS] Proxy status use cases #29789
RebeccaTamachiro merged 11 commits into
productionfrom
rebecca/dns-proxy-status-use-and-limits

Conversation

@RebeccaTamachiro

@RebeccaTamachiro RebeccaTamachiro commented Apr 13, 2026

Copy link
Copy Markdown
Contributor

Summary

PCX-21286
PCX-20722

  • Adds a new /use-cases/ reference page to the DNS proxy status section, covering when to proxy records and when to use DNS-only.
  • Updates the proxy status overview with sections on request size limits and connection timeouts, and adds a "When to use DNS-only" entry point linking to the new page.
  • Expands the limitations page with a cross-reference to the use cases page, clarifies wording around proxy eligibility, and explains why NTLM authentication breaks behind the proxy.

@github-actions github-actions Bot added product:dns Issues or PRs related to DNS size/m labels Apr 13, 2026
@github-actions

Copy link
Copy Markdown
Contributor

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern Owners
/src/content/docs/dns/ @RebeccaTamachiro, @cloudflare/pcx-technical-writing, @cloudflare/product-owners

@RebeccaTamachiro RebeccaTamachiro marked this pull request as ready for review April 14, 2026 16:40
@RebeccaTamachiro RebeccaTamachiro requested a review from a team April 14, 2026 16:40

### Connection timeouts

Cloudflare enforces a default [Proxy Read Timeout](/fundamentals/reference/connection-limits/) of 120 seconds between Cloudflare and your origin server. If your origin does not send an HTTP response within this window, Cloudflare returns a [524 error](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/error-524/). Enterprise customers can [increase the timeout value](/cache/how-to/cache-rules/settings/#proxy-read-timeout-enterprise-only).

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if we should reference the actual number here. What if we change it? How do we know to also change it here (and not only in the referenced page)?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a good call 👍 I removed the duplicated table but missed this one. Thank you!

Comment thread src/content/docs/dns/proxy-status/use-cases.mdx Outdated

Cloudflare does not proxy SMTP traffic on port 25 by default. Proxying a record that handles email traffic causes mail servers to connect to Cloudflare's IP addresses instead of your mail server. This prevents email delivery.

Use a dedicated hostname for email that is separate from your proxied web traffic hostname. If your MX record points to the same hostname as your website, Cloudflare creates a `dc-#####` record to route email traffic directly to your origin. Refer to [Email issues](/dns/troubleshooting/email-issues/) for details.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Use a dedicated hostname for email that is separate from your proxied web traffic hostname. If your MX record points to the same hostname as your website, Cloudflare creates a `dc-#####` record to route email traffic directly to your origin. Refer to [Email issues](/dns/troubleshooting/email-issues/) for details.
Use a dedicated hostname for email that is separate from your proxied web traffic hostname. If your MX record points to the same hostname as your website, Cloudflare dynamically prepends `dc-#####` to the hostname in the response for the MX record to route email traffic directly to your origin. Refer to [Email issues](/dns/troubleshooting/email-issues/) for details.

or something similar that indicates that Cloudflare doesn't create a new record, but dynamically injects something into the response. Will dm you with more details, Rebecca.

Comment thread src/content/docs/dns/proxy-status/index.mdx Outdated
Comment thread src/content/docs/dns/proxy-status/use-cases.mdx Outdated
Co-authored-by: ranbel <101146722+ranbel@users.noreply.github.com>
@RebeccaTamachiro RebeccaTamachiro enabled auto-merge (squash) April 21, 2026 08:04
@RebeccaTamachiro RebeccaTamachiro merged commit f671ba2 into production Apr 21, 2026
11 checks passed
@RebeccaTamachiro RebeccaTamachiro deleted the rebecca/dns-proxy-status-use-and-limits branch April 21, 2026 08:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

product:dns Issues or PRs related to DNS size/m

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants