01
Subdomain Setup: DNS, Routing, and HTTPS
Plan a subdomain as a complete public endpoint: choose the record, prepare host routing, account for DNS caches, and verify TLS and application behavior.
Practical reference library
These guides focus on the handoffs where deployments usually fail: naming, DNS records, provider routing, cache timing, certificates, and the final public response.
Search runs locally in your browser. No query is sent to a search provider or stored by and.guide.
15 guides available
01 · Foundations
Start here if records, caching, local names, or the difference between a hostname and an application route are still fuzzy.
01
Plan a subdomain as a complete public endpoint: choose the record, prepare host routing, account for DNS caches, and verify TLS and application behavior.
02
Compare direct IPv4 records with hostname aliases, including CNAME coexistence and zone-apex constraints, provider-specific alias features, and verification steps.
03
Understand why DNS answers differ after a change, how TTL and negative caching affect what resolvers return, and how to separate authoritative DNS from recursive and application issues.
04
Configure a Cloudflare DNS record with an explicit target, proxy decision, accurate TTL expectations, and checks for both DNS and the public application path.
06
Use custom domains locally without turning your setup into a guessing game. This guide covers hosts files, local DNS, HTTPS, and when to use a real public subdomain.
02 · Publishing
Platform-specific walkthroughs for moving from a provider preview URL to a stable public hostname with HTTPS.
07
Connect a Cloudflare Pages project to a custom subdomain, verify DNS, and avoid the routing mistakes that make a working deployment look broken.
08
Point a Vercel project at a custom domain without confusing DNS ownership, project routing, HTTPS issuance, and redirect behavior.
09
Set a GitHub Pages custom domain, verify DNS, enable HTTPS, and avoid stale CNAME and certificate problems.
10
Connect a Netlify site to a custom hostname, verify the active DNS record, and finish with a clean HTTPS rollout.
03 · Operations
Naming, wildcard behavior, certificate authorization, stable tunnels, and cleanup practices for a domain that has to last.
05
Separate the public-name decision from the connectivity decision, compare current ngrok development domains with owned hostnames, and choose an appropriate route to a local or hosted service.
11
Choose a public hostname with a purpose-owner-lifecycle worksheet, a practical naming rubric, and an expiry plan for previews and temporary environments.
12
Design wildcard DNS without confusing DNS reachability, application host routing, and the one-label coverage of TLS wildcard certificates.
13
Understand why the zone apex cannot be an ordinary CNAME, how flattening and provider Alias features synthesize address answers, and how to verify and roll back the real target.
14
Configure CAA without accidentally blocking certificate renewal: trace inheritance, understand issuewild precedence, and test the exact CA and hostname set used by your platform.
15
Build an owner-backed inventory of public hostnames, choose the correct keep, protect, redirect, or retire state, and verify cleanup without leaving broken DNS or stale search results behind.
Try a broader term such as DNS, HTTPS, domain, Cloudflare, or local development.