DNS, Cloudflare proxy, and origin reachability
Lab 1 established the foundational Cloudflare configuration required for the website to resolve, proxy through Cloudflare, and serve traffic through the intended hostname.
Demonstrable content
Validate DNS and Cloudflare reachability with:
dig www.ybarra-cflab.com
curl -I https://www.ybarra-cflab.com/\
A successful result should show that the hostname resolves and that HTTP responses are being
delivered through Cloudflare.
What was completed
- Configured the lab domain in Cloudflare DNS.
- Validated hostname resolution for the public website.
- Confirmed Cloudflare was in the request path.
- Established the baseline for later routing and Pages work.
Technical summary
We configured DNS records for the lab hostname and validated that requests to the site were resolving correctly through Cloudflare. This created the foundation for proxying, inspection, routing, and later Cloudflare Pages deployment. The key technical outcome was proving that the hostname could be resolved and reached through Cloudflare rather than treating the origin as the only control point.
Customer-facing summary
We connected the website domain to Cloudflare so Cloudflare could sit in front of the site and help control how traffic is routed, secured, and delivered. This is the first step in making the website easier to manage, troubleshoot, and protect.