01
subdomains 1990Company Editorial Desk
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.
DNS · HTTPS · public hostnames
Make the hostname the boring part of your launch.
and.guide explains the path from a name in a DNS dashboard to a working HTTPS response—without collapsing records, routing, certificates, and cache timing into one vague “propagation” problem.
- 15 focused technical guides
- Primary-source references
- Visible review and update dates
- A public correction channel
Three learning paths
Start where your deployment stopped.
- 01
Choose the record
Understand A, AAAA, CNAME, flattening, TTL, and what a public resolver can actually see.
Start with DNS records - 02
Connect the platform
Keep DNS ownership, provider host binding, redirects, and certificate issuance as separate checks.
Connect a custom domain - 03
Verify the public path
Use resolver answers and HTTP headers to distinguish cache timing from routing and TLS failures.
Follow the full rollout
Editor’s starting points
Featured guides
Six entry points covering the full path from record choice to public cleanup.
View the full library02
A Records and CNAME Records: Choosing a DNS Target
Compare direct IPv4 records with hostname aliases, including CNAME coexistence and zone-apex constraints, provider-specific alias features, and verification steps.
04
cloudflare 1990Company Editorial Desk
Cloudflare DNS: Records, Proxy Status, and Verification
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
development 1990Company Editorial Desk
Local Development with Custom Domains
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.
11
subdomains 1990Company Editorial Desk
Subdomain Naming Rules for Public Projects
Choose a public hostname with a purpose-owner-lifecycle worksheet, a practical naming rubric, and an expiry plan for previews and temporary environments.
15
operations 1990Company Editorial Desk
Public Subdomain Inventory and Cleanup Runbook
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.
Editorial method
How each guide is maintained.
Read the editorial policy- 01
Start with the failure
Each guide is organized around a real decision or failure boundary instead of a broad keyword summary.
- 02
Prefer primary sources
Product-specific behavior is checked against vendor documentation, standards, or project documentation.
- 03
Show the verification
Commands and illustrative outputs make it clear what to inspect, what an answer means, and what it does not prove.
- 04
Keep corrections public
Published, updated, and source-review dates are visible, with a direct path for reporting technical errors.
A secondary service
Need a carefully named project address on and.guide?
The site also accepts limited subdomain requests. Names and project context are reviewed manually; availability checks are not a promise of approval or provisioning.