Skip to content

Commit 1104d1c

Browse files
authored
[ZT] override_doh_endpoint parameter (#21991)
* pcx-16811 * remove unused component
1 parent 80c0e5c commit 1104d1c

File tree

1 file changed

+7
-1
lines changed
  • src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment

1 file changed

+7
-1
lines changed

src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/parameters.mdx

+7-1
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ sidebar:
77

88
---
99

10-
import { GlossaryTooltip } from "~/components"
10+
import { GlossaryTooltip} from "~/components"
1111

1212
Each client supports the following set of parameters as part of their deployment, regardless of the deployment mechanism.
1313

@@ -122,6 +122,12 @@ The string must be a valid IPv4 or IPv6 address, otherwise the WARP client will
122122

123123
### `override_doh_endpoint`
124124

125+
:::note
126+
Only supported in Gateway with DoH mode.[^1]
127+
:::
128+
129+
[^1]: Gateway with WARP is supported in client version 2025.2.664.0 and below. In version 2025.4.589.1 and above, this parameter does not apply to Gateway with WARP because all DoH traffic goes inside of the WARP tunnel.
130+
125131
Overrides the [IP address](/cloudflare-one/connections/connect-devices/warp/deployment/firewall/#doh-ip) used by the WARP client to resolve DNS queries via DNS over HTTPS (DoH). If you set this parameter, be sure to update your organization's firewall to ensure the new IP is allowed through.
126132

127133
This functionality is intended for use with a Cloudflare China local network partner or any other third-party network partner that can maintain the integrity of network traffic. Most IT admins should not set this setting as it will redirect all DoH traffic to a new IP.

0 commit comments

Comments
 (0)