[SSL] add troubleshooting for conflicting _acme-challenge records in direct Cloudflare zone - #33304
Merged
Merged
Conversation
ngayerie
requested review from
a team,
baubuchon-cf,
dinasaur404,
irvinebroque and
lgarofalo
as code owners
September 8, 2026 14:52
Contributor
Review✅ No issues found in commit Code ReviewThis code review is in beta and may not always be helpful — use your judgment. No code review issues found. ConventionsNo convention issues found. Style Guide ReviewNo style-guide issues found. CommandsOnly codeowners can run commands. Post a comment with the command to trigger it.
|
github-actions
Bot
added
product:ssl
Contributor
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
Collaborator
Author
|
[AI] Triage of bot findings — fixing all 3 (no skips):
Pushing a fix commit now. |
🚀 Deploying Preview to Cloudflare 🚀Preview URL: https://ssl-saas-dcv-conflicting-txt-records.previews.developers.cloudflare.com (commit c7e0d86)This URL reflects your latest Preview deploymentPreview Deployments by commit
|
Contributor
Collaborator
Author
|
[AI] Triage of latest bot review on commit
Pushing a fix commit now. |
Collaborator
Author
|
[AI] SG-4b559d5150c8: ✅ Fixing — rewriting passive voice on line 19 in active voice. |
Collaborator
Author
|
[AI] CR-89c4a73d7fa4: ✅ Fixing — adding the |
Collaborator
Author
|
[AI] SG-f0c7f14de46e + SG-8514f13b21bf: ✅ Fixing both — wrapping bare |
baubuchon-cf
approved these changes
Sep 8, 2026
baubuchon-cf
left a comment
baubuchon-cf
left a comment
Collaborator
There was a problem hiding this comment.
LGTM. Verified the TXT-record persistence claim against the COMS source (cleanup logic explicitly skips TXT records it didn't place) — root cause checks out. Dig commands and anchors are correct. Approving.
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
5 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.
Adds documentation for Issue 2 from the certificate DCV support analysis (DEE-3645).
What: Expands the existing
dcv-conflicting-recordspartial and adds a new "Conflicting_acme-challengeTXT records" section to the SaaS certificate validation troubleshooting page.Why: When a customer's domain is simultaneously present in a direct Cloudflare zone and onboarded as a custom hostname via a SaaS provider (Cloudflare for SaaS), a hardcoded
_acme-challengeTXT record in the direct zone overrides the DCV delegation CNAME. This causes certificate validation to remain stuck atpending_validationwith no actionable error message. The issue is invisible to both the SaaS operator and the end customer — the docs previously did not document this scenario or how to resolve it.