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 1 commit
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 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 Nate (FDQN) within Gateway Egress policies.
Copy link
Contributor

@kennyj42 kennyj42 Apr 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it worth including a screenshot of the feature configured?

Copy link
Contributor Author

@Encore-Encore Encore-Encore Apr 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As powerful as the feature is, its just a selector addition so not much to show off UI wise unfourtunley

Copy link
Contributor

@cdisher cdisher Apr 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't that make it easier to choose a screenshot then? It makes it crystal clear where the feature exists instead of customers needing to "figure it out" since we have a lot of selectors. Great way to easily help with the distribution and product association problem.

Here's a great example from a recent announcement that is basically just a selector: https://developers.cloudflare.com/changelog/2025-04-09-workers-timing/

- Host, Domain, Content Categories, and Application selectors are now available in the Gateway Egress policy builder in beta
- During the beta period this will apply to traffic on-ramped via the WARP client, Proxy Endpoints (commonly deployed via PAC files), or 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.