Skip to content

Commit e82fcbd

Browse files
committed
Apply feedback
1 parent 44631d5 commit e82fcbd

File tree

2 files changed

+7
-5
lines changed

2 files changed

+7
-5
lines changed

src/content/docs/cloudflare-one/policies/gateway/egress-policies/dedicated-egress-ips.mdx

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,6 @@ sidebar:
88
import { Details } from "~/components";
99

1010
:::note
11-
1211
Only available as an add-on to Zero Trust Enterprise plans.
1312
:::
1413

@@ -41,7 +40,11 @@ When testing against another origin, you may see either an IPv4 or IPv6 address.
4140

4241
## Bring your own IP address (BYOIP)
4342

44-
Enterprise users can provide an IP address for a private DNS resolver to use as a dedicated egress IP. Gateway supports bringing your own IPv4 and IPv6 addresses.
43+
Enterprise users can use their own authority-provided IPv4 and IPv6 addresses as dedicated egress IPs. Gateway supports bringing your own IPv4 and IPv6 addresses.
44+
45+
After you onboard your IP addresses, the IP addresses will appear when you create a [egress policy](/cloudflare-one/policies/gateway/egress-policies/) and choose **Use dedicated egress IPs (Cloudflare or BYOIP)** as the [egress method](/cloudflare-one/policies/gateway/egress-policies/#egress-methods). BYOIP dedicate egress IPs do not support [IP geolocation](#ip-geolocation).
46+
47+
For more information, refer to [Cloudflare BYOIP](/byoip/) or contact your account team.
4548

4649
## Limitations
4750

@@ -69,7 +72,6 @@ When creating egress policies with dedicated egress IPs, set your secondary IPv4
6972
### IP geolocation
7073

7174
:::note
72-
7375
IP geolocation will take at least six weeks to update across databases.
7476
:::
7577

src/content/docs/cloudflare-one/policies/gateway/egress-policies/index.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -47,9 +47,9 @@ Since Gateway policies evaluate from [top to bottom](/cloudflare-one/policies/ga
4747

4848
Choose one of the following options for your egress policy:
4949

50-
- **Default Cloudflare egress**: uses the default source IP range shared across all Zero Trust accounts. Ensures the most performant Internet experience as user traffic egresses from the nearest Cloudflare data center.
50+
- **Use default Cloudflare egress method** uses the default source IP range shared across all Zero Trust accounts. Ensures the most performant Internet experience as user traffic egresses from the nearest Cloudflare data center.
5151

52-
- **Dedicated Cloudflare egress IPs** uses the primary IPv4 address and IPv6 range selected in the dropdown menus. You can optionally specify a secondary IPv4 address in a different data center. If the primary data center goes down, Gateway will egress from the secondary data center to avoid traffic drops during reroutes. There is no need for a secondary IPv6 because IPv6 traffic can egress from any Cloudflare data center. To learn more about IPv4 and IPv6 egress behavior, refer to [Egress locations](/cloudflare-one/policies/gateway/egress-policies/dedicated-egress-ips/#egress-location).
52+
- **Use dedicated egress IPs (Cloudflare or BYOIP)** uses the primary IPv4 address and IPv6 range selected in the dropdown menus. You can optionally specify a secondary IPv4 address in a different data center. If the primary data center goes down, Gateway will egress from the secondary data center to avoid traffic drops during reroutes. There is no need for a secondary IPv6 because IPv6 traffic can egress from any Cloudflare data center. Dedicated egress IPs can be provided by either Cloudflare or [BYOIP](/cloudflare-one/policies/gateway/egress-policies/dedicated-egress-ips/#bring-your-own-ip-address-byoip). To learn more about IPv4 and IPv6 egress behavior, refer to [Egress locations](/cloudflare-one/policies/gateway/egress-policies/dedicated-egress-ips/#egress-location).
5353

5454
## Selectors
5555

0 commit comments

Comments
 (0)