Skip to content

Conversation

@Vortexmind
Copy link
Contributor

Some users might want to use Cloudflare as public primary and their DNS infrastructure as hidden secondary for DR purposes. Clarify that this is also possible.

Some users might want to use Cloudflare as public primary and their DNS infrastructure as hidden secondary for DR purposes. 
Clarify that this is also possible.
@Vortexmind Vortexmind requested review from a team and RebeccaTamachiro as code owners May 29, 2025 09:39
@github-actions github-actions bot added size/xs product:dns Issues or PRs related to DNS labels May 29, 2025
@hyperlint-ai
Copy link
Contributor

hyperlint-ai bot commented May 29, 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

Clarified the option to use Cloudflare as a public primary DNS with a hidden secondary for disaster recovery purposes.

  • Specified that users can configure Cloudflare as a public primary DNS and their own DNS as a hidden secondary for disaster recovery.
  • Added a note about not enabling multi-provider DNS if Cloudflare is the only public primary.
  • Updated instructions to reflect the new configuration options.

Modified Files

  • src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/setup.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.

@RebeccaTamachiro RebeccaTamachiro enabled auto-merge (squash) June 5, 2025 10:19
@RebeccaTamachiro RebeccaTamachiro merged commit 6c69297 into cloudflare:production Jun 5, 2025
5 checks passed
@workers-devprod workers-devprod added the contribution [Holopin] Recognizes a docs contribution, big or small label Jun 5, 2025
@holopin-bot
Copy link

holopin-bot bot commented Jun 5, 2025

Congratulations @Vortexmind, the maintainer of this repository has issued you a holobyte! Here it is: https://holopin.io/holobyte/cmbj8j5mj509007jolv6wyhlx

This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account.
Or if you're new to Holopin, you can simply sign up with GitHub, which will do the trick!

sdnts pushed a commit to sdnts/cloudflare-docs that referenced this pull request Jul 24, 2025
* Clarify additional option

Some users might want to use Cloudflare as public primary and their DNS infrastructure as hidden secondary for DR purposes. 
Clarify that this is also possible.

* Slight adjustment following PM review

---------

Co-authored-by: Rebecca Tamachiro <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

contribution [Holopin] Recognizes a docs contribution, big or small product:dns Issues or PRs related to DNS size/xs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants