Developers
Troubleshooting
Start from the observed state, collect evidence, and avoid destructive changes.
#Overview
Start from the observed state, collect evidence, and avoid destructive changes.
#Diagnose by layer
Start with the external symptom, UTC time, and one precise URL. Then check authoritative resolution, propagation, zone state, certificate, POP selection, origin, WAF, cache, and application response in that order.
For API and CLI, capture HTTP status, message, CLI version, and configuration source without a token. For WireGuard, check interface, peers, routes, ACLs, and POP readiness without publishing keys.
#Minimum evidence
Reproduce with a non-destructive request.
Compare an authoritative and a public recursive resolver.
Record zone/file/task identifier and displayed states.
Apply one correction, wait for synchronization, and retest.
#Verifiable example
dig NS example.com +short
curl -I https://example.com/
cdn-pizza config