DNS & Routing
Routing overview
Section titled “Routing overview”Static frontends are served from Cloudflare Pages. Traffic never reaches the Hetzner VPS for those hostnames — Cloudflare terminates TLS at the edge and serves pre-built files from its CDN.
User → docs.pablorosi.dev / pablorosi.dev → Cloudflare DNS → Pages project → edge CDN → dist/DNS records
Section titled “DNS records”After creating a Pages project, Cloudflare provides a target hostname (e.g. <project>.pages.dev). Point the custom domain with:
| Type | Name | Content | Proxy |
|---|---|---|---|
| CNAME | docs | <project>.pages.dev | Proxied |
The pablorosi.dev and docs.pablorosi.dev domains are added under Pages → Custom domains in the Cloudflare dashboard. The zone lives on the same account, so Cloudflare creates the DNS record automatically.
Hostname map
Section titled “Hostname map”| Hostname | Destination | Notes |
|---|---|---|
docs.pablorosi.dev | Cloudflare Pages | Documentation site (Astro + Starlight) |
pablorosi.dev | Cloudflare Pages | Portfolio (Astro Vanilla) |
docs.pablorosi.com | Cloudflare edge redirect | 301 → docs.pablorosi.dev |
Legacy .com domains are handled by Redirect Rules at the Cloudflare edge. Only the final .dev hostname needs a Pages custom domain.
Cloudflare Pages provisions and renews TLS certificates for custom domains automatically. No origin certificate or reverse proxy configuration is required on the server for static frontends.