Article · Halo
DNS and hosting explained without the jargon
A plain-English map of where your site lives, how the domain finds it, and what you actually own.
Three pieces: name, signpost, and home
Your domain is the human-friendly name people remember. DNS is the directory that maps that name to servers. Hosting is where your HTML, assets, and application code run. Problems are painful when those pieces are split across accounts nobody can access.
We document who owns each layer and keep registrar, DNS, and hosting credentials in your hands. That way you are never stuck negotiating with a vendor who claims they “own” your domain while you pay the bills.
DNS records you will actually touch
A records and CNAME records point your domain or subdomains to the right place. MX records route email—change them carefully or mail stops flowing. TXT records prove ownership for tools like Google Search Console or SPF for email authenticity.
Misconfigured DNS propagates slowly and is easy to break under pressure. Before cutovers, we snapshot existing values, plan rollback, and verify with TTL in mind so you are not guessing during business hours.
Hosting is not interchangeable commodity
Some hosts oversell shared pools; others offer solid state storage and modern TLS defaults but weak support. We match hosting to your traffic, compliance needs, and whether you need staging environments or automated deploys.
SSL certificates should renew automatically. Backups should be restorable—not hypothetical. If your provider cannot answer where backups live and how to restore, that is a red flag before you ever need a rescue.
When things go wrong
Email breaks, certificates expire, or a migration half-completes. A clear map of DNS and hosting turns chaos into a checklist. We prefer teaching clients the map over keeping them dependent—transparency is part of the service.