Skip to content

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

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

Open
grstnhbr wants to merge 1 commit into
base: production
Choose a base branch
from
+1 −1
Open

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

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
2 changes: 1 addition & 1 deletion src/content/partials/cloudflare-one/gateway/create-resolver-policy.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,4 +78,4 @@ When a user's query matches a resolver policy, Gateway will send the query to yo
2. Private resolvers behind the default virtual network for your account
3. Private resolvers behind a custom virtual network

Gateway will cache the fastest resolver for use in subsequent queries. Resolver priority is cached on a per user basis for each data center.
Within each of the three above scenarios, 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.
Loading