[Cloudflare One] Fix incorrect resolver selection description in resolver policies

[grstnhbr]

What

Fixes an inaccuracy in the resolver policies documentation. The docs stated that Gateway caches the fastest resolver for subsequent queries. This is not how the system works.

Actual behavior

Gateway selects a resolver at random using uniform traffic distribution within each category (public, private-default-vnet, private-custom-vnet). If the selected resolver does not respond in time, Gateway attempts the next resolver based on observed round-trip time. Queries are staggered, not sent all at once.

The FastServer algorithm exists in EdgeDNS but is not used by gateway-resolver for custom resolvers.

Change

In src/content/partials/cloudflare-one/gateway/create-resolver-policy.mdx:

Before:

Gateway will cache the fastest resolver for use in subsequent queries. Resolver priority is cached on a per user basis for each data center.

After:

Within each category, Gateway selects a resolver at random using uniform traffic distribution. If the selected resolver does not respond in time, Gateway will attempt the next resolver based on observed round-trip time.

Context

This was identified by the Gateway engineering team during investigation of customer DNS resolution behavior with resolver policies.

[cloudflare-docs-bot]

Review

⚠️ 1 warning found in commit d72afb4.

👉 Fix in your agent 👈

Fix the following review findings in PR #32601 (https://github.com/cloudflare/cloudflare-docs/pull/32601).

Before making changes, review each finding and present a brief summary table:
- For each finding, state whether you agree, disagree, or need clarification
- If you disagree (e.g. the fix requires disproportionate effort for minimal benefit,
  or the finding is factually incorrect), explain why
- If you need clarification before deciding, ask those questions
- Then share your plan for which issues to tackle and in what order

After triaging, follow this order:
1. Post a comment on this PR for any findings you are skipping, with the finding ID and your reasoning.
2. Then commit the fixes for the legitimate findings.

The comment must come before the commit — the bot reads PR comments when a new
push triggers a review, so skip comments posted after the push will be missed.

---

## Style Guide Review

### Warnings (1)

#### SG-323aa40cc09e · Directional words
- **File:** `src/content/partials/cloudflare-one/gateway/create-resolver-policy.mdx` line 81
- **Issue:** Line contains "Within each of the three above scenarios"
- **Fix:** Replace the directional word "above" with a direct reference, e.g., "Within each of these three scenarios" or "Within each of the three scenarios described earlier."

Code Review

This code review is in beta and may not always be helpful — use your judgment.

_{No code review issues found.}

Conventions

_{No convention issues found.}

Style Guide Review

Warnings (1)

File	Issue
partials/cloudflare-one/gateway/create-resolver-policy.mdx line 81	Directional words — Line contains "Within each of the three above scenarios" Fix: Replace the directional word "above" with a direct reference, e.g., "Within each of these three scenarios" or "Within each of the three scenarios described earlier."

Commands

Only codeowners can run commands. Post a comment with the command to trigger it.

Command	Description
/review	Runs a review now. Incremental if a prior review exists, full if not.
/full-review	Re-reviews the entire PR diff from scratch, ignoring incremental history. Useful after a rebase, when you want a fresh review, or if the bot gets out of sync and reports issues that no longer exist.
/ignore-review-limit	Permanently lifts the 2-review automatic limit for this PR. Future pushes will trigger reviews as normal.
/disable-auto-review	Stops automatic reviews from triggering on future pushes to this PR. Codeowners can still run /review or /full-review manually.
/rebase	Rebases the PR branch against production. On conflict, attempts to resolve automatically using AI. Stops with an explanation if confidence is not high enough.