-
Notifications
You must be signed in to change notification settings - Fork 10.2k
[DNS] Call out differences between standard vs advanced NS #23504
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.
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
RebeccaTamachiro
merged 14 commits into
production
from
rebecca/dns-advanced-ns-behavior
Aug 1, 2025
Merged
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
c2d4116
Introduce new limitations section for advanced NS
RebeccaTamachiro da1a3bf
Expand to more general considerations and move to setup.mdx
RebeccaTamachiro fab2b3a
Text review and add example DNS table for delegation
RebeccaTamachiro dfe34d8
Re-add note on Advanced NS vs Custom NS to concept page
RebeccaTamachiro 9dbdbde
Use specific header for more emphasis and better linking
RebeccaTamachiro 459ff3b
Nest DNSSEC keys under Advanced NS in Foundation DNS features
RebeccaTamachiro 379645e
Add note on advanced ns vs custom in account-custom-nameservers
RebeccaTamachiro 984d455
Further clarify advanced-vs-custom NS and align with UI messaging
RebeccaTamachiro f6c5193
Revert "Nest DNSSEC keys under Advanced NS in Foundation DNS features"
RebeccaTamachiro 060b029
Merge branch 'production'
RebeccaTamachiro 61d7284
Replace 'zone' by 'account' in features list
RebeccaTamachiro 643fb6c
Create dedicated page explaining Foundation DNSSEC keys
RebeccaTamachiro 37b56e6
Add clarification on how to get unique DNSSEC keys
RebeccaTamachiro 0341a33
Apply suggestions from code review
RebeccaTamachiro File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,17 @@ | ||
| --- | ||
| pcx_content_type: reference | ||
| title: DNSSEC keys | ||
| sidebar: | ||
| order: 5 | ||
|
|
||
| --- | ||
|
|
||
| With [Foundation DNS](/dns/foundation-dns/), you can request that the ZSK/KSK pair that is used for [DNSSEC](/dns/dnssec/) is unique to your Cloudflare account. To opt in to this feature, contact your account team. | ||
|
|
||
| All zones within your Cloudflare account - regardless of using [standard](/dns/nameservers/#standard-nameservers) or [advanced nameservers](/dns/foundation-dns/advanced-nameservers/) - will use the dedicated Zone Signing Key (ZSK) and Key Signing Key (KSK) for DNSSEC. These keys are set at the account level. | ||
|
|
||
| ## Further reading | ||
|
|
||
| For more background information, refer to [How DNSSEC works](https://www.cloudflare.com/learning/dns/dnssec/how-dnssec-works/). | ||
|
|
||
| For details about DNSSEC settings at Cloudflare, refer to the [DNSSEC documentation](/dns/dnssec/). |
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we still using monospace for DNS record types? (e.g. TXT, A, AAAA, etc.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We added an exception for cases where there are several inline occurrences in a roll or for hyperlinks (since the style would make it look like two separate links). This was following a team critique a while ago.