Skip to content
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

PDNS Secure Location Management New User Role #21049

Open
wants to merge 8 commits into
base: production
Choose a base branch
from

Conversation

NuelEdeh
Copy link
Contributor

Summary

Changelog to update Gateway DNS Secure Locations Write Role

Screenshots (optional)

Documentation checklist

  • The documentation style guide has been adhered to.
  • If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
  • Files which have changed name or location have been allocated redirects.

@NuelEdeh NuelEdeh requested review from a team as code owners March 21, 2025 20:04
Updated based on reviewers comments
Copy link
Contributor

hyperlint-ai bot commented Mar 25, 2025

Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment.

We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally.


PR Change Summary

Introduced a new user role for managing secure DNS locations in Cloudflare Zero Trust.

  • Added a new Cloudflare Zero Trust Secure DNS Locations Write role for government customers.
  • Outlined security requirements for managing DNS locations, including mandatory BYO IP usage and source network filtering.
  • Provided guidelines for role assignment and avoiding conflicts with broader permission roles.

Added Files

  • src/content/changelog/gateway/2025-03-21-pdns-user-locations-role.mdx

How can I customize these reviews?

Check out the Hyperlint AI Reviewer docs for more information on how to customize the review.

If you just want to ignore it on this PR, you can add the hyperlint-ignore label to the PR. Future changes won't trigger a Hyperlint review.

Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add hyperlint-ignore to the PR to ignore the link check for this PR.

What is Hyperlint?

Hyperlint is an AI agent that helps you write, edit, and maintain your documentation.

Learn more about the Hyperlint AI reviewer and the checks that we can run on your documentation.

Copy link
Contributor Author

@NuelEdeh NuelEdeh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated this changelog to be more concise and clear.

@NuelEdeh
Copy link
Contributor Author

@kennyj42 please see the new updates!

Updated copy "Bring your own DNS resolver IP addresses"
Copy link
Contributor Author

@NuelEdeh NuelEdeh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Bring Your Own (BYO) IPv4/IPv6 Resolver Ranges" feels clunky.

Changed to: "Bring your own DNS resolver IP addresses"

@NuelEdeh NuelEdeh requested a review from kennyj42 March 25, 2025 18:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants