[Gateway] DNS resolver BYOIP #19183
Merged
[Gateway] DNS resolver BYOIP #19183
+26
−22
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
maxvp
requested review from
RebeccaTamachiro,
a team,
kokolocomotion1 and
ranbel
as code owners
![hyperlint-ai[bot]](https://avatars.githubusercontent.com/in/718456?s=60&v=4){kind=small}
|
|
||
| Gateway uses the public source IPv4 address of your network to identify your DNS location, apply policies and log DNS requests. Unless you have purchased a [dedicated IPv4 resolver IP](#dns-resolver-ip), you must provide source IP addresses for the IPv4 traffic you want to filter with DNS policies. Otherwise, Gateway will not be able to attribute the traffic to your account. | ||
| When you create a DNS location, Gateway will resolve queries over IPv4 with the default DNS resolver IP addresses. These addresses are Anycast IP addresses shared across every Cloudflare Zero Trust account. To resolve queries over IPv6, your location will receive and use a unique DNS resolver IPv6 address. These IP addresses are how Gateway will match DNS queries to locations and apply the appropriate filtering rules. |
There was a problem hiding this comment.
Suggested change
| When you create a DNS location, Gateway will resolve queries over IPv4 with the default DNS resolver IP addresses. These addresses are Anycast IP addresses shared across every Cloudflare Zero Trust account. To resolve queries over IPv6, your location will receive and use a unique DNS resolver IPv6 address. These IP addresses are how Gateway will match DNS queries to locations and apply the appropriate filtering rules. | |
| When you create a DNS location, Gateway will resolve queries over IPv4 with the default DNS resolver IP addresses. These addresses are anycast IP addresses shared across every Cloudflare Zero Trust account. To resolve queries over IPv6, your location will receive and use a unique DNS resolver IPv6 address. These IP addresses are how Gateway will match DNS queries to locations and apply the appropriate filtering rules. |
Issues:
- Style Guide - (Terms-error) Use 'anycast' instead of 'Anycast'.
Fix Explanation:
The term 'Anycast' should be changed to 'anycast' to comply with the style guide's capitalization rules. This change does not affect code references or templating language syntax, so it is safe to apply.
|
|
||
| If you are on the Enterprise plan, you have the option of manually entering one or more source IP addresses of your choice. This enables you to create Gateway DNS locations even if you are not connecting from any of those networks' IP addresses. | ||
| Enterprise users can request a dedicated DNS resolver IPv4 address to be provisioned for a DNS location instead of the default Anycast addresses. Queries forwarded to that address will be identified using the dedicated DNS resolver IPv4 address. |
There was a problem hiding this comment.
Suggested change
| Enterprise users can request a dedicated DNS resolver IPv4 address to be provisioned for a DNS location instead of the default Anycast addresses. Queries forwarded to that address will be identified using the dedicated DNS resolver IPv4 address. | |
| Enterprise users can request a dedicated DNS resolver IPv4 address to be provisioned for a DNS location instead of the default anycast addresses. Queries forwarded to that address will be identified using the dedicated DNS resolver IPv4 address. |
Issues:
- Style Guide - (Terms-error) Use 'anycast' instead of 'Anycast'.
Fix Explanation:
The term 'Anycast' should be lowercase 'anycast' as per the style guide recommendation. This is a straightforward capitalization correction.
Deploying cloudflare-docs with
|
| Latest commit: |
db94fc1
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://d5ab472a.cloudflare-docs-7ou.pages.dev |
| Branch Preview URL: | https://max-gw-byoip-locations.cloudflare-docs-7ou.pages.dev |
ranbel
approved these changes
Jan 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PCX-11117