Skip to content

Commit ec6afe5

Browse files
Update src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/index.mdx
Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com>
1 parent a67020c commit ec6afe5

File tree

1 file changed

+1
-1
lines changed
  • src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic

1 file changed

+1
-1
lines changed

src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ sidebar:
55
order: 6
66
---
77

8-
When the WARP client is deployed on a device, Cloudflare will process all DNS queries and network traffic by default. However, under certain circumstances, you may need to exclude specific DNS queries or network traffic from WARP. For example, you may need to resolve an internal hostname with a private DNS resolver instead of CLoudflare's [public DNS resolver](1.1.1.1/).
8+
When the WARP client is deployed on a device, Cloudflare will process all DNS queries and network traffic by default. However, under certain circumstances, you may need to exclude specific DNS queries or network traffic from WARP. For example, you may need to resolve an internal hostname with a private DNS resolver instead of Cloudflare's [public DNS resolver](1.1.1.1/).
99

1010
There are four options you can configure to exclude traffic from WARP:
1111

0 commit comments

Comments
 (0)