Scenario
Wildcard issuance fails for one delegated subzone while the provider confirms the TXT record is present.
A cert-manager DNS01 challenge hits the right zone and still fails because propagation checks read the parent delegation path
The TXT record exists, but the solver validates through a slower delegation branch.
What to check first
- Identify the primary failure signal in the The TXT Record Existed and the Solver Kept Looking Through the Parent's Window scenario.
- Separate visible symptoms from the underlying technical dependency.
- Describe the safest recovery path and the follow-up prevention work.
Checking checklist
- Summarize the current impact and the last known change.
- Collect direct evidence from logs, runtime state, and configuration before changing anything.
- Separate immediate recovery from permanent prevention work.
Recovery and prevention
Check delegation and propagation path before increasing wait times or rotating credentials.
Questions worth viewing together
No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.
State the root cause, the evidence that supports it, and the safest recovery direction.
The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.
Similar cases seen in the field