WT$ is DNS (and Why Should You Care)?

Somewhere in your business, there is a system that controls where your emails are delivered, whether your website loads, and how the outside world finds you online. It has been running silently, without anyone thinking about it, for years.

It is called DNS. And unless something goes wrong, you will never hear about it.

DNS stands for Domain Name System. In simple terms, it is the address book of the internet. When someone sends you an email, DNS tells their system where to deliver it. When a client types your website address into a browser, DNS tells the browser where to find it. When your security tools verify that an email genuinely came from your company, DNS is what they check.

Every business that uses email, has a website, or operates online depends on DNS. Every single one. And most have no idea who manages it, where it is configured, or what would happen if someone changed it.

We know this because we have seen it go wrong.

A director at a business we work with noticed an email had not arrived. Just one. He called us. We checked — nothing in spam, no bounce back, the email simply was not there. Within a few hours, more people reported the same thing. Then more. Email had stopped arriving across the business.

We knew immediately what had happened. We had seen the pattern before. Something had changed in the DNS records.

The problem was — we did not manage their DNS. One of the directors had always held the credentials himself. He was on holiday. Unreachable. And before he left, he had handed the login to the marketing team so they could make a small change to the website.

They made the change. It took seconds. Nobody told them that the same system that controls the website also controls email delivery. Nobody told them because nobody in the business understood that connection existed.

The emails stopped. The website went dark. And the one person who understood the setup was fishing.

We fixed it that night. The technical fix took minutes. But the real problem — no process for changes, no documentation of what the records do, no understanding of how critical DNS is to the business, credentials handed over without context — that stayed exactly as it was.

It is probably still there now.

Three questions worth asking

If you are running a business and you are not sure about the answers to these, that uncertainty is the answer.

Who manages your DNS? Not who registered the domain ten years ago. Who actively manages the records today? Is it your IT provider? A director who set it up once? A web agency? If you do not know, nobody is managing it.

Who has the login? DNS credentials are often shared informally — handed to a web developer, given to a marketing team member, saved in someone's browser. If you cannot say with confidence who has access and who does not, you have a security gap.

What would happen if someone changed a record tomorrow? Would your IT provider know? Would anyone check before the change was made? Would you find out when it broke, or before?

Why this matters more than it used to

DNS is increasingly a compliance issue, not just a technical one. Proper email authentication — SPF, DKIM, and DMARC — all depend on DNS records being correctly configured and actively managed. These are not obscure technical details. They are what stops someone sending emails that look like they came from your company. They are what email providers check when deciding whether to deliver your messages or send them to spam.

The UK Cyber Security and Resilience Bill, progressing toward enforcement, will bring managed service providers and their clients into scope for compliance obligations that include exactly this kind of infrastructure oversight. If your DNS is not managed, documented, and controlled — you have a gap that is going to become harder to ignore.

The uncomfortable truth

DNS is the kind of thing that works perfectly until it does not. And when it stops working, it stops everything — email, website, client communication, reputation. The fix is usually simple. The damage from the hours or days it takes to find the right person, get the right access, and understand what changed — that is where the real cost lives.

Most businesses do not need to understand how DNS works. But every business needs to know that someone competent is looking after it, that changes go through a process, and that the credentials are not sitting in someone's browser history.

If you are not sure whether that is true for your business — that is worth a conversation.

‍