Independent technical publication

Practical DNS guides for teams publishing under real hostnames.

and.guide publishes focused guides about subdomains, DNS, HTTPS, Cloudflare setup, and local-to-public workflows. A manual request flow exists, but the core surface is the guide library.
  • Fifteen indexed guides centered on DNS, HTTPS, and hostname decisions
  • Real operator identity, editorial desk, and working policy pages
  • Screens, command output, and rollout checklists instead of filler summaries
  • Manual review stays available, but it is not the site's only reason to exist

Featured guides

Read the full library before you request a hostname. The goal is to make the public address, DNS setup, HTTPS rollout, and hosting decision feel concrete before review starts.
View all guides

March 5, 2026

Complete Guide to Subdomain Setup

Set up a subdomain the safe way: choose the right record type, point it at the correct destination, verify propagation, and finish with HTTPS.

Read guide

March 6, 2026

DNS A Record vs CNAME

Understand the real difference between A records and CNAME records, when each is appropriate, and the mistakes that cause confusing DNS behavior.

Read guide

March 7, 2026

Understanding DNS Propagation Time

DNS propagation is mostly about cache expiry, not mystery. Learn what really changes after a DNS update and how to verify progress without guesswork.

Read guide

March 8, 2026

How to Configure Cloudflare DNS

A practical Cloudflare DNS setup guide covering record creation, proxy mode, TTL choices, and the checks that prevent common rollout mistakes.

Read guide

March 9, 2026

Replace NGROK with Free Subdomains

A stable subdomain is often a better public address than a rotating tunnel URL. Learn when that is true, when it is not, and how to choose safely.

Read guide

March 10, 2026

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.

Read guide

April 22, 2026

Cloudflare Pages Custom Domain Setup

Connect a Cloudflare Pages project to a custom subdomain, verify DNS, and avoid the routing mistakes that make a working deployment look broken.

Read guide

April 23, 2026

Vercel Custom Domain DNS Setup

Point a Vercel project at a custom domain without confusing DNS ownership, project routing, HTTPS issuance, and redirect behavior.

Read guide

April 24, 2026

GitHub Pages Custom Domain and HTTPS

Set a GitHub Pages custom domain, verify DNS, enable HTTPS, and avoid stale CNAME and certificate problems.

Read guide

April 25, 2026

Netlify Custom Domain DNS Setup

Connect a Netlify site to a custom hostname, verify the active DNS record, and finish with a clean HTTPS rollout.

Read guide

April 26, 2026

Subdomain Naming Rules for Public Projects

Choose subdomain names that stay clear, specific, and reviewable across docs, apps, APIs, status pages, previews, and staging environments.

Read guide

April 27, 2026

Wildcard Subdomains: When to Use Them

Understand when wildcard DNS is useful, when it creates review risk, and how to verify wildcard behavior before public launch.

Read guide

April 28, 2026

CNAME Flattening Explained

Learn what CNAME flattening does, why apex domains are special, and how to verify flattened answers without losing track of the real target.

Read guide

April 29, 2026

CAA Records and Let's Encrypt

Use CAA records to state which certificate authorities may issue for your domain, then verify issuance rules before HTTPS rollout.

Read guide

April 30, 2026

How to Audit Indexed Subdomains Before Review

Audit public subdomains before an advertising or search review so staging pages, test posts, template demos, and server errors do not define the domain.

Read guide

The request flow is secondary. The guides are there to make public naming decisions sharper.

Manual review, not instant setup

and.guide is for thoughtful requests that need a stable public name, not disposable throwaway endpoints.

Clear naming and guardrails

Reserved names, misleading labels, and fake platform claims are filtered out before a request moves forward.

Fifteen practical flagship guides

The public library now stays focused on DNS, HTTPS, hosting platforms, staging cleanup, and local-to-public publishing.

Naming directions

Names people can remember.

These are not promises of instant availability. They are examples of the kind of calm, specific naming that tends to survive review and still make sense six months later.

quiet-lab.and.guide
field-notes.and.guide
build-journal.and.guide
maker-studio.and.guide
research-room.and.guide
preview-desk.and.guide
tool-notes.and.guide
signal-lab.and.guide
release-manual.and.guide
team-journal.and.guide
design-room.and.guide
project-notes.and.guide
quiet-lab.and.guide
field-notes.and.guide
build-journal.and.guide
maker-studio.and.guide
research-room.and.guide
preview-desk.and.guide
tool-notes.and.guide
signal-lab.and.guide
release-manual.and.guide
team-journal.and.guide
design-room.and.guide
project-notes.and.guide

Trust signals that should have been there from the start

The public site now has to support both the product and the review process. That means cleaner policies, tighter scope, and fewer empty claims.
  • Subdomain requests are manually reviewed, not auto-approved.
  • The request flow is limited to the root domain, not a sprawling public network.
  • Guides stay focused on DNS, HTTPS, subdomains, and public project workflows.
  • 1990Company is named publicly as the site operator, with working contact and policy pages.
  • No fake uptime guarantees, fake support tiers, or pretend global offices.