Skip to content

[Gateway] Update EDNS behavior #22888

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 1 commit into from
Jun 4, 2025
Merged

[Gateway] Update EDNS behavior #22888

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion src/content/partials/cloudflare-one/gateway/add-locations.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ To add a DNS location to Gateway:
3. Choose a name for your DNS location.
4. Choose at least one [DNS endpoint](/cloudflare-one/connections/connect-devices/agentless/dns/locations/#dns-endpoints) to resolve your organization's DNS queries.
5. (Optional) Toggle the following settings:
- **Enable EDNS client subnet** sends a user's IP geolocation to authoritative DNS nameservers. <GlossaryTooltip term="EDNS Client Subnet (ECS)" link="/cloudflare-one/glossary/?term=ecs">EDNS Client Subnet (ECS)</GlossaryTooltip> helps reduce latency by routing the user to the closest origin server. Cloudflare enables EDNS in a privacy preserving way by not sending the user's exact IP address but rather a `/24` range which contains their IP address.
- **Enable EDNS client subnet** sends a user's IP geolocation to authoritative DNS nameservers. <GlossaryTooltip term="EDNS Client Subnet (ECS)" link="/cloudflare-one/glossary/?term=ecs">EDNS Client Subnet (ECS)</GlossaryTooltip> helps reduce latency by routing the user to the closest origin server. Cloudflare enables EDNS in a privacy preserving way by not sending the user's exact IP address but rather the first `/24` range of the larger range that contains their IP address. This `/24` range will share the same geographic location as the user's exact IP address.
- **Set as Default DNS Location** sets this location as the default DoH endpoint for DNS queries.
6. Select **Continue**.
7. (Optional) Turn on source IP filtering for your configured endpoints, then add any source IPv4/IPv6 addresses to validate.
Expand Down