From d72afb47106dae2800d448b6de00839cb8f1e84b Mon Sep 17 00:00:00 2001 From: aj Date: Fri, 7 Aug 2026 08:53:54 -0500 Subject: [PATCH] [Cloudflare One] Fix incorrect resolver selection description in resolver policies The documentation incorrectly stated that Gateway caches the fastest resolver for subsequent queries. In practice, Gateway selects a resolver at random using uniform traffic distribution within each category (public/private), and falls back to the next resolver based on round-trip time if the selected one does not respond. --- .../partials/cloudflare-one/gateway/create-resolver-policy.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/partials/cloudflare-one/gateway/create-resolver-policy.mdx b/src/content/partials/cloudflare-one/gateway/create-resolver-policy.mdx index 40817932e7d..958eb40c956 100644 --- a/src/content/partials/cloudflare-one/gateway/create-resolver-policy.mdx +++ b/src/content/partials/cloudflare-one/gateway/create-resolver-policy.mdx @@ -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.