DNS is the internet's address book. It's the quiet system that turns your web address — like yourshop.com — into the actual location of the computer that holds your website, so visitors land in the right place. You rarely think about it, until something stops working.
What is DNS, really?
Every website and mailbox lives on a computer somewhere — a server — and every server has a numeric address called an IP address, something like 192.0.2.10. Those numbers are how machines find each other, but nobody wants to remember them. So we use friendly names instead: yourshop.com rather than a string of digits.
DNS (the Domain Name System) is what connects the two. When someone types your web address, their device quietly asks DNS, "Which server holds this?" DNS replies with the address, and the browser goes there. It's exactly like looking up a business in a phone book to get its number — except it happens in a fraction of a second, billions of times a day, without anyone noticing.
Here's the useful mental picture: your domain name is your shopfront sign, and DNS is the directory that tells the world which building the sign belongs to. Move to a new building, and you update the directory. Get the directory wrong, and people show up at an empty lot.
Where DNS records live
Your DNS settings sit in one place — usually with whoever you bought your domain from (your registrar) or your web host. That control panel is often called the "DNS zone" or "DNS records." Inside it is a short list of entries, each pointing a part of your name at a destination. You may never open it yourself; often your web agency or host manages it for you. But it's worth knowing it exists, because almost every "the website is down" or "our email vanished" story traces back to a change made here.
The common records, in plain terms
You don't need to memorise these. But recognising the names helps when a host or developer mentions them:
- A record — points your web address to the server that hosts your website. This is the entry that says "
yourshop.comlives at this address." If it's wrong or missing, your site won't load. - MX record — points your domain's email to the right mail server. MX stands for "mail exchange." It's what makes sure a message to
you@yourshop.comreaches your inbox and not somewhere else. Break this, and email stops arriving. - TXT record — a small note of plain text attached to your domain. TXT records are used for lots of behind-the-scenes checks: proving your email is really from you (settings called SPF, DKIM and DMARC), confirming to Google that you own the site, and more. They're invisible to visitors but quietly important.
- CNAME record — a forwarder that says "this name is really an alias for that name." Often used so
www.yourshop.compoints to the same place asyourshop.com.
That's the whole toolkit for most small businesses: a couple of records that keep your site reachable, one that keeps your email flowing, and a few text notes that keep everything trusted.
Why DNS matters for your business
DNS sits underneath three things you absolutely rely on:
- Your website being reachable. If the record pointing to your site is wrong, visitors get an error instead of your shop — even though the site itself is perfectly healthy. The building is fine; the sign points to the wrong street.
- Your email arriving. Email routing depends entirely on DNS. A mistyped or deleted mail record can silently stop messages from reaching you, and customers assume you're ignoring them.
- Your security certificate. The little padlock in the browser bar (an SSL certificate) is issued and renewed based on DNS proving you control the domain. If DNS is misconfigured, certificates can fail to renew, and visitors then see a scary "Not secure" warning.
In other words, DNS is invisible when it works and very visible when it doesn't. Most business owners only meet it during a crisis — which is the worst time to learn what it is.
What breaks when DNS is wrong
DNS problems are frustrating because everything looks fine from the inside. A few common ones:
- The site won't load for anyone but you. Often because a record was changed and hasn't fully spread yet. DNS updates aren't instant — they can take anywhere from a few minutes to a day or so to reach everyone, a delay called propagation.
- Email suddenly stops. A changed mail record, or a domain moved to a new host without copying the old settings across, and inbound messages quietly bounce or disappear.
- The domain "expired" and the site went dark. If a domain isn't renewed, its DNS stops answering and everything attached to it — website and email — goes down at once.
- The padlock warning appears. A certificate that couldn't renew because of a DNS mix-up leaves visitors staring at a browser warning that makes your shop look unsafe.
The tricky part is that these failures are often silent. Nothing emails you to say "your email records changed" or "your certificate didn't renew." You find out when a customer does — unless something is watching on your behalf.
Do I need to manage DNS myself?
Mostly, no. For a typical small business or webshop, DNS is set up once — by your host, your web agency, or the person who built your site — and then left alone. The risk isn't day-to-day management; it's that changes happen (a new email provider, a site migration, a new tool), and nobody checks that the underlying records still line up. That's where quiet breakage creeps in.
The healthy approach is simple: leave the records to the people who set them up, but have something keeping an eye on the outcomes — is the site loading, is email protected, is the certificate valid — so a bad change gets noticed in hours, not weeks.
Where TrustCtrl fits
TrustCtrl doesn't manage your DNS or change any records — it watches the results from the outside, so you find out fast when something built on DNS stops working. There's nothing to install. WatchControl checks that your website is up and responding, and keeps an eye on the services behind it — including your mail server — emailing you when something goes down and again when it recovers. MailControl checks whether your email is protected and trusted and reads the settings that live in your DNS records, giving you copy-ready fixes when something's off. CertControl finds every certificate you have — even forgotten ones — and warns you 30 and 10 days before one expires, so a DNS-related renewal slip never turns into a public "Not secure" warning. Each finding comes in plain language with steps to fix it, in a simple view for you and a technical view for your developer. It's free during early access.
Is DNS the same as web hosting?
No, though they're often bought from the same company. Web hosting is the actual building where your website lives — the server that stores your pages. DNS is the directory that tells the world which building to visit. You can host your site in one place and keep your DNS somewhere else. They work together, but they're separate jobs, which is why a site can be perfectly hosted yet unreachable because of a DNS mistake.
Why is my website not updating after a DNS change?
Because DNS changes don't reach everyone at once. When you update a record, the new information spreads across the internet gradually — a delay called propagation that usually takes from a few minutes up to around a day. During that window, some visitors see the new setup and others still see the old one. If a change hasn't taken effect for you after 24 to 48 hours, that's when it's worth checking whether the record was actually saved correctly.
Can a DNS problem take down my email as well as my website?
Yes, and it often does. Website and email both rely on DNS records under the same domain, so a single mistake — an expired domain, a botched migration, a deleted record — can knock out both at the same time. That's why it helps to monitor them together: if your domain wobbles, you want to know your site and your inbox are affected, not discover each problem separately from an unhappy customer.
What's a TXT record used for?
A TXT record is a short piece of plain text attached to your domain that machines can read. It doesn't affect what visitors see. Its most important job today is email trust: TXT records hold the settings (called SPF, DKIM and DMARC) that let receiving mail servers confirm a message really came from you and isn't a forgery. They're also used to prove domain ownership to services like Google. Small entries, but they quietly protect your reputation.