Skip to content

Commit 4960b96

Browse files
authored
Update Zero Trust IP addresses
1 parent ce486e0 commit 4960b96

File tree

1 file changed

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

1 file changed

+5
-0
lines changed

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

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -49,6 +49,11 @@ Many Cloudflare Zero Trust services rely on traffic going through WARP, such as
4949

5050
## Cloudflare Zero Trust IP addresses
5151

52+
If you are using Split Tunnels in Include mode and have [DNS policies](cloudflare-one/policies/gateway/dns-policies/) with the block page enabled, you must include the IPs that blocked domains will resolve to. Unless you are using a [dedicated or BYOIP resolver IP](cloudflare-one/connections/connect-devices/agentless/dns/locations/dns-resolver-ips/#dns-resolver-ip) this will be:
53+
54+
- `162.159.36.12`
55+
- `162.159.46.12`
56+
5257
In [Secure Web Gateway without DNS filtering](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-modes/#secure-web-gateway-without-dns-filtering) WARP mode, you cannot [add domains](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/#cloudflare-zero-trust-domains) to the Split Tunnel. If you are using Split Tunnels in Include mode, you must include the IPs that resolve to `<your-team-name>.cloudflareaccess.com` instead:
5358

5459
- `104.19.194.29`

0 commit comments

Comments
 (0)