[DNS] Review and reorganize FAQ #27798
Open
+252
−289
Conversation
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
Contributor
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
Contributor
Contributor
|
This PR requires additional review attention because it affects the following areas: RedirectsThis PR changes current filenames or deletes current files. Make sure you have redirects set up to cover the following paths:
PartialsThis PR updates partial files, which are pieces of content used across multiple files in our Render component.
|
RebeccaTamachiro
changed the title
RebeccaTamachiro
requested review from
dinasaur404 and
irvinebroque
as code owners
ranbel
reviewed
Jan 23, 2026
|
|
||
| ## Old SaaS provider content after updating a CNAME | ||
|
|
||
| When switching SaaS providers, an older configuration can take precedence if the old provider provisioned a specific custom hostname and the new provider provisioned a wildcard custom hostname. This is expected as per the [certificate and hostname priority](https://developers.cloudflare.com/ssl/reference/certificate-and-hostname-priority/#hostname-priority). |
Contributor
There was a problem hiding this comment.
Suggested change
| When switching SaaS providers, an older configuration can take precedence if the old provider provisioned a specific custom hostname and the new provider provisioned a wildcard custom hostname. This is expected as per the [certificate and hostname priority](https://developers.cloudflare.com/ssl/reference/certificate-and-hostname-priority/#hostname-priority). | |
| When switching SaaS providers, an older configuration can take precedence if the old provider provisioned a specific custom hostname and the new provider provisioned a wildcard custom hostname. This is expected as per the [certificate and hostname priority](/ssl/reference/certificate-and-hostname-priority/#hostname-priority). |
ranbel
reviewed
Jan 23, 2026
| ## How does DNS Firewall choose a backend nameserver to query upstream? | ||
|
|
||
| </Details> | ||
| DNS Firewall alternates between a customer's nameservers, using an algorithm is more likely to send queries to the faster upstream nameservers than slower nameservers. |
Contributor
There was a problem hiding this comment.
Suggested change
| DNS Firewall alternates between a customer's nameservers, using an algorithm is more likely to send queries to the faster upstream nameservers than slower nameservers. | |
| DNS Firewall alternates between a customer's nameservers, using an algorithm that is more likely to send queries to the faster upstream nameservers than slower nameservers. |
ranbel
reviewed
Jan 23, 2026
|
|
||
| import { Render, DashButton } from "~/components"; | ||
|
|
||
| The sections bellow cover frequently asked questions about Cloudflare authoritative DNS. For DNS Firewall, refer to [DNS Firewall FAQ](/dns/dns-firewall/faq/). |
Contributor
There was a problem hiding this comment.
Suggested change
| The sections bellow cover frequently asked questions about Cloudflare authoritative DNS. For DNS Firewall, refer to [DNS Firewall FAQ](/dns/dns-firewall/faq/). | |
| The sections below cover frequently asked questions about Cloudflare authoritative DNS. For DNS Firewall, refer to [DNS Firewall FAQ](/dns/dns-firewall/faq/). |
ranbel
reviewed
Jan 23, 2026
|
|
||
| `Error: failed to create DNS record: HTTP status 403: Authentication error (10000)` | ||
|
|
||
| This is caused by an error in your code syntax, when your are not using index `[0]` for the zones. Find an example below and a more detailed thread on [GitHub](https://github.com/cloudflare/terraform-provider-cloudflare/issues/913). |
Contributor
There was a problem hiding this comment.
Suggested change
| This is caused by an error in your code syntax, when your are not using index `[0]` for the zones. Find an example below and a more detailed thread on [GitHub](https://github.com/cloudflare/terraform-provider-cloudflare/issues/913). | |
| This is caused by an error in your code syntax, when you are not using index `[0]` for the zones. Find an example below and a more detailed thread on [GitHub](https://github.com/cloudflare/terraform-provider-cloudflare/issues/913). |
ranbel
approved these changes
Jan 23, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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-20392
Follow-up to #27322