A website can be perfectly healthy and still appear completely dead.

The server is running. The database is fine. Nobody deployed bad code. Yet your browser says the site cannot be reached, and suddenly a team is refreshing dashboards like they are trying to restart the internet through concentration.

Sometimes the problem is DNS.

DNS is one of those pieces of technology that people ignore for years because it works quietly. Then it fails, and half the company discovers that a domain name is not the website. It is more like the signpost telling your device where the website lives.

We built the internet around names humans can remember

People like names such as example.com. Networks prefer numerical addresses and routes.

DNS sits between those worlds.

When you type a domain into a browser, your device needs to find out which system should receive the request. That answer may come from a local cache, your router, your internet provider or another DNS resolver. The details vary, but the basic job is simple: turn a name into useful routing information.

Because this happens constantly and quickly, it feels invisible.

That invisibility creates a strange assumption. People think “the website” is one thing. In reality, reaching a modern site may depend on domain registration, DNS records, content delivery networks, certificates, cloud infrastructure and several external services before the page has a chance to render.

The logo is one thing. The path to the logo is not.

A typo in one record can have a very large audience

DNS changes often look tiny.

Someone edits a record. A domain points somewhere new. Email settings are updated. A company moves traffic from an old service to a new one.

The change might be one line.

The consequences can affect every user.

This is why experienced teams treat DNS changes with more respect than the interface suggests. A control panel can make the action look like editing a spreadsheet cell. It is not. You may be changing where customers, email systems or APIs go when they look for your domain.

And because DNS information is cached, mistakes do not always disappear the moment you fix them. Different users may see different answers for a while.

Distributed systems have a talent for making “I already changed it back” feel less reassuring than it sounds.

Your DNS provider is part of your security perimeter

Domain security does not get enough attention outside technical teams.

If someone gains control of your DNS, they may be able to redirect traffic, interfere with email or point users toward systems you do not own. The exact impact depends on what else is protected, but the position is powerful.

That means the account controlling DNS deserves serious security: strong authentication, limited administrator access and a clear record of who can make changes.

I would put it in the same mental category as cloud administrator access or the account that manages your company email.

Yet many small organisations have domains registered under an employee’s personal email address because that was convenient eight years ago.

Convenience has an impressive memory.

If you run a business, check who actually controls the domain. Not who everyone assumes controls it. Who can log in today, reset the account and modify the DNS records?

It is a boring question until the answer surprises you.

DNS is also a privacy conversation now

Traditional DNS queries were not designed with modern privacy expectations in mind. A resolver can potentially learn which domain names a device is trying to reach.

Newer approaches such as encrypted DNS can protect those queries while they travel between your device and the resolver. Browsers and operating systems increasingly support this in some form.

That is useful, but it does not make browsing invisible. The destination may still know you visited. Your network may observe other information. Accounts, cookies and browser fingerprints still exist.

Privacy technology has a bad habit of being sold as invisibility.

Encrypted DNS solves a narrower problem: it can stop ordinary DNS queries from travelling in plain view across the network path to the resolver.

Narrow improvements are still improvements.

The fastest DNS is not always the best DNS

People sometimes change DNS providers because a benchmark says one is a few milliseconds faster.

Fair enough. Performance matters.

But I care about reliability, privacy policy, security features and support as well. For a company, I care about access control and change history. For a family, I may care about filtering options. For a developer, I may care about how quickly changes propagate and how easy records are to manage safely.

The technically fastest answer is not always the operationally best answer.

This is a recurring lesson in technology. We optimise the number that is easiest to measure and then discover the important problem lived somewhere else.

Email depends on DNS more than most people realise

DNS is not just about websites.

Email systems use DNS records to decide where messages should go and to help verify whether a sending system is authorised. Misconfigured records can cause mail to fail, land in spam or become easier to impersonate.

This is why a company can move its website successfully and still discover two days later that contact forms, newsletters or staff email are behaving strangely.

The domain is shared infrastructure.

Changing one part without understanding the others is a good way to create a Friday evening problem.

Most users should not think about DNS every day

That is the funny part.

A well-designed layer of infrastructure should disappear. You should type a name and arrive at the right place. Nobody wants a pop-up explaining recursive resolution before opening Gmail.

But if you build, run or own anything on the internet, DNS deserves a place in your mental map.

Know where it is managed. Protect the account. Document important records. Make changes carefully. Do not let the only person who understands the setup be someone who left the company three years ago.

And when a website appears dead, remember that the website may be perfectly fine.

Sometimes the signpost fell over.