Project context
The setting
A WordPress environment had issues outside the dashboard, spanning domain routing, hosting, SSL, redirects, and Cloudflare behaviour.
Challenge
The problem to solve
Incorrect A and CNAME records, SSL handshake failures, cache-purge issues, and routing conflicts can produce similar symptoms while requiring different fixes.
My role and scope
What I was responsible for
I investigated the request path from DNS through Cloudflare and hosting, corrected the identified configuration faults, and checked the affected site journeys.
Investigation and reasoning
- Reviewed A, CNAME, and routing records
- Traced SSL handshake and origin-hosting behaviour
- Checked CDN cache, purge, and redirect configuration
Approach and implementation
- Corrected the identified DNS and routing conflicts
- Resolved SSL configuration issues within the recorded scope
- Adjusted Cloudflare CDN, WAF, cache, and redirect settings where relevant
- Rechecked important pages after the changes
Technical Scope
Technical Scope & Verification
Factual records of infrastructure troubleshooting, security hardening, and operational scope completed.
The recorded infrastructure faults were resolved. A previously shown 100% availability result has been removed because the portfolio contains no observation period or independent availability report.
- Layers reviewed
- DNS / SSL / CDN
- Outcome
- Recorded faults resolved
Evidence note
Existing DNS, hosting, SSL, and Cloudflare troubleshooting record. Raw change logs and monitoring reports are not stored in the portfolio.
Constraints and lessons
What this work made clear
- Infrastructure symptoms should be traced layer by layer
- Availability percentages need a defined measurement period and source