DNS and CDN for Cloudflares
DNS and CDN is Cloudflare's entry layer. Its authoritative DNS answers lookups for your domain, and proxied records route traffic through Cloudflare's network, where static content is cached in data centres near visitors. This reduces origin load and latency, and it hides the origin server's real IP address.
Stage: Edge Basics · Part of the Cloudflare roadmap · Last reviewed 19 November 2026
What to learn in DNS and CDN
- Add a domain to Cloudflare and change the nameservers at the registrar
- Explain the difference between proxied and DNS-only records
- Write Cache Rules that cache static assets and bypass dynamic pages
- Purge cached files by URL or tag after a deployment
- Read cache status headers such as cf-cache-status to debug a miss
DNS and CDN interview questions
What does the orange cloud mean on a Cloudflare DNS record?
It means the record is proxied: DNS returns Cloudflare IP addresses and requests pass through Cloudflare, so caching, security rules and TLS apply. A grey cloud, or DNS-only, returns the origin address directly and bypasses those features.
How do you debug a page that should be cached but is not?
Check the cf-cache-status header for MISS, BYPASS or DYNAMIC, then look at the response's Cache-Control and Set-Cookie headers and your cache rules. HTML is not cached by default, so you must define a rule for it.
Where DNS and CDN fits in the Cloudflare roadmap
DNS and CDN belongs to the Edge Basics stage (beginner level), which takes about 14 hours. Networking and delivery.
Other units in this stage
Back to the full Cloudflare roadmap