DNS

DNS stands for Domain Name System. Every domain name, whether it is yourbusiness.com or a subdomain like shop.yourbusiness.com, needs to be translated into the technical address that a server actually understands. DNS is the translation layer that does that job, and it runs constantly, in the background, every time anyone types your address into a browser or sends you an email.

A domain’s DNS is really a small set of records. One kind points your bare domain and www address at the server that hosts your site. Another points your email at whoever handles your mail. Others exist to prove ownership, to enable HTTPS, or to authorise a third-party service to send email on your behalf. None of this is visible to a visitor. They just type your address and the page appears, or they send an email and it lands.

The records themselves live with whichever provider is set as your domain’s nameservers. That is the detail that actually matters to a business owner, more than the technical mechanics of how lookups happen.

Why it matters to you

DNS is quiet until it breaks, and when it breaks it breaks everything at once. Get one record wrong and your site can go dark, or your email can start bouncing, while nothing else about your business changes. Because it sits underneath the website, the hosting and the email all at the same time, whoever controls it effectively controls whether any of those things work.

That is also why DNS control is an ownership question, not just a technical one. A vendor who quietly holds your DNS can move your site, your email or your ads however they like, and you would have no way to stop them without going through that vendor first.

How I set it up

I move a client’s DNS into a Cloudflare zone inside an account the client owns, not one that sits under my name or an agency’s. From there, DNS, hosting and mail routing all run through the same dashboard, which cuts down on the number of places something can quietly go wrong. Every record gets written down as part of the handover, so if the relationship ever ends, the next person can see exactly what points where.

I keep the record set as small and as boring as possible. Fewer records mean fewer things to break, and fewer things a future edit can knock over by accident.

What it looks like in practice

Day to day, DNS is invisible. You will never open that dashboard unless something changes, like adding a new mail provider or pointing a subdomain at a new tool. When that day comes, the change is usually a single record, made once, and it takes effect everywhere within minutes to a few hours as the update spreads across the internet.