Skip to content

Create 2025-04-28-FDQN-Filtering-Egress-Policies.mdx #22031

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

Merged
merged 4 commits into from
Apr 28, 2025
Merged

Create 2025-04-28-FDQN-Filtering-Egress-Policies.mdx #22031

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
ea55bc1
Create 2025-04-28-FDQN-Filtering-Egress-Policies.mdx
Encore-Encore Apr 28, 2025
442fcba
Update src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress…
Encore-Encore Apr 28, 2025
78ca5a8
Update src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress…
Encore-Encore Apr 28, 2025
f7e2b14
Update src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress…
Encore-Encore Apr 28, 2025
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
15 changes: 15 additions & 0 deletions src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
---
title: FQDN Filtering For Gateway Egress Policies
description: Select your egress IP depending on your upstream fully qualified domain name (FQDN), application, or category
products:
- gateway
hidden: false
date: 2025-04-28T11:00:00Z
---

Cloudflare One administrators can now control which egress IP is used based on a destination's fully qualified domain name (FDQN) within Gateway Egress policies.
- Host, Domain, Content Categories, and Application selectors are now available in the Gateway Egress policy builder in beta.
- During the beta period, you can use these selectors with traffic on-ramped to Gateway with the WARP client, proxy endpoints (commonly deployed with PAC files), or Cloudflare Browser Isolation.
- For WARP client support, additional configuration is required. For more information, refer to the [WARP client configuration documentation](/cloudflare-one/policies/gateway/egress-policies/#limitations).

This will help apply egress IPs to your users' traffic when an upstream application or network requires it, while the rest of their traffic can take the most performant egress path.