What DNS Actually Is (and the Week It Cost a Client Her Email)

A client lost her email for a week. Nothing was hacked. A company she had never heard of owned her domain, it lapsed, and her email went down with it.

She didn't know that company existed. She didn't know you rent a domain instead of buying it. She found out both things in the worst possible way, on a Tuesday, when her mail stopped arriving and nobody could tell her why.

Here is what she was never told. It's the same thing most people who hire a developer are never told.

A domain isn't one thing. It's three.

When you say "my domain," you're talking about three separate layers, and each one can be held by a different company.

1. The registrar is who you rent the name from. Namecheap, GoDaddy, Cloudflare. You don't own a domain the way you own a chair. You rent it, usually a year at a time, and it renews. Miss the renewal and it can lapse.

2. The DNS provider is the phone book. Or if you've never used one, it's your phone's contacts: a name that quietly knows the address so you don't have to. When someone types your name, DNS looks it up and says where to go: website over here, email over there. Change the phone book and you change where everything points.

3. The application is where it actually lands. Your website on Wix. Your email on Google Workspace. Your store on Shopify.

Now look at what's hanging off that middle layer in the diagram. Not just your website. Your email too. That's the part almost nobody knows, and it's exactly what bit my client.

Why her email died with her domain

When the domain lapsed, the phone book went blank. The website was the obvious casualty. The email was the expensive one.

Email runs on DNS records too, quiet little entries called MX records that say "mail for this name goes here." When the domain dropped, those records went with it. No records, no email.

She thought a domain was the website. It's the phone book for everything with her name on it, and when it went, it took the mail with it.

Changes aren't instant

One more thing to know, because it trips people up. When you change DNS, it doesn't happen right away. The internet remembers the old answer for a while, and how long it remembers is set by a number called the TTL, the time to live.

That's the whole thing you need about TTL: changes take time to take effect. It isn't broken, it's caching. Which is why you never move your domain or switch hosts five minutes before a launch. Give it a day.

The part that actually matters

Go back to the diagram. Three layers, and there's one question that belongs under each: who controls this?

For my client, the honest answer was "a company I've never heard of." Her domain had been set up years ago by someone who'd long since moved on, parked at a provider she didn't know existed, quietly renewing on a card she couldn't see. Until the day it didn't.

That is not rare. It's common, especially with older setups, and it usually isn't anyone being shady. It's an arrangement made a long time ago that nobody cleaned up or wrote down.

Here's what you can actually do about it. It's the whole reason I wrote this.

The one thing to check

For each of the three layers, ask one question: whose account is this in, and could I log into it right now?

Your registrar. Your DNS. Your website and email hosting. Three logins. If you have all three, you own your online presence. You can move it, fix it, or fire whoever manages it without asking anyone's permission. If you can't answer for even one of them, that isn't a small gap. That's the layer that takes your email down for a week while you go find out who a company you've never heard of actually is.

You don't have to run any of this yourself. You just have to know where it lives and be able to get in.

Outsource the work. Never outsource the keys.