Closed
Conversation
Contributor
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
Contributor
|
|
||
| ## Enable enforce DNS-only | ||
|
|
||
| Use the [Update DNS Settings](/api/resources/dns/subresources/settings/subresources/account/methods/edit/) endpoint to enable enforce DNS-only for your account: |
Contributor
There was a problem hiding this comment.
Which API permissions / member roles are required for this? I hope it's only SuperAdmins :)
Contributor
There was a problem hiding this comment.
Since this is a new field on the existing endpoint, the permissions remain the same as those required for modifying other DNS settings, specifically, read/write access to DNS Record resources.
smittal123
reviewed
Mar 24, 2026
Contributor
smittal123
left a comment
smittal123
left a comment
There was a problem hiding this comment.
Added Exceptions sections
| - **Account-level**: Affects all zones in the account simultaneously. | ||
| - **Non-destructive**: Does not modify your DNS records. Disabling the setting restores normal proxy behavior. | ||
| - **API-only**: Available through the API only, not in the Cloudflare dashboard. | ||
|
|
Contributor
There was a problem hiding this comment.
Exceptions
Records Not Affected by the Proxy Kill Switch:
- Spectrum applications – these are already grey-clouded CNAME records pointing to Spectrum endpoints and see no impact
- Cloudflare for SaaS fallback origin records – default origin for custom hostnames
- Cloudflare for SaaS eyeball zone records – records pointing to SaaS providers (bypassing won't help if the SaaS provider's target remains proxied)
- Workers custom domains – orange-clouded A records pointing to
100:: - R2 custom domains – orange-clouded CNAME records pointing to
public.r2.dev - Web3 gateways – Ethereum and IPFS DNSlink gateways (CNAMEs to
ethereum.cloudflare.com/ipfs.cloudflare.com) - Cloudflare Tunnel (Argo Tunnel) records – Records required for tunnel routing (grey-clouding may break tunnel connectivity)
Included:
- Proxied Load Balancer records – The kill switch applies to LB records
Contributor
|
CI run failed: build logs |
Contributor
Author
|
Had some issues while trying to address the build fail so moving to #29353 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Summary
PCX-21243