What DNS Actually Means for Your Dealership (And Why You Should Care Who Controls Yours)

From the “Just Enough to Be Dangerous” series — short videos that teach you enough to spot trouble, not enough to break something yourself.

Someone says, “It’s a DNS problem,” and everyone in the room nods like they know what that means. Most of them don’t. And most of them shouldn’t have to.

But somebody at your dealership absolutely has to know what DNS is, where it lives, and who can change it. If that person is “whoever set it up five years ago and is no longer with us,” you have a problem — and you probably won’t find out until something breaks.

Let me explain why DNS matters to you, even if you’ll never touch it.

DNS is the phone book. But the analogy is too simple.

Yes, DNS is the internet’s phone book. When someone types yourdealership.com into a browser, DNS is what tells the browser “that domain lives at this IP address.” Without DNS, your website doesn’t exist as far as the internet is concerned.

But the phone book analogy undersells how many things at your dealership quietly depend on it.

Your website, sure. But also:

• Your email — every email you send and receive runs through DNS records.
• Your CRM — DealerSocket, VinSolutions, eLeads, or whatever you use. They live at subdomains like crm.yourdealership.com or crm.dealersocket.com and they have to be reachable.
• Your DMS integrations — if you use CDK, Reynolds, Tekion, or Dealertrack, those integrations are stitching together systems that all have to find each other through DNS.
• OEM portals — manufacturer-required systems (recall notifications, warranty claims, vehicle allocations, dealer-locator feeds) often require specific DNS records to work properly.
• Marketing tools — Google Analytics, Meta pixels, call tracking numbers, third-party chat widgets, lead providers like Cars.com, AutoTrader, CarGurus — each of them touches your DNS one way or another.
• Single sign-on and identity — if your team uses Microsoft 365 or Google Workspace, the auto-discovery service that makes Outlook “just work” is a DNS record.

So DNS isn’t a phone book for one thing. It’s the phone book for the entire digital dealership. And it has hundreds of entries.

Why DNS is uniquely fragile at dealerships

A typical dealership has more DNS records than most small businesses. The reason is that you’ve accumulated vendors over the years, and most vendors wanted something from your DNS.

Here’s what usually happens:

1. A website vendor set up the website. They have login access to your DNS.
2. An IT company took over. They added Microsoft 365 records. They have login access too.
3. A marketing agency added tracking pixels and a new landing page. They needed a CNAME, so they got login access.
4. The website vendor left, and nobody changed the password.
5. Your domain registrar is whoever the original owner’s brother-in-law recommended in 2014.
   

Now you have a domain with potentially dozens of records, multiple people with access (some of whom no longer work for you or any vendor), and a single point of failure: the person who knows the password to the registrar account.

And one more thing: dealerships turn over staff more than most industries. The person who set everything up is rarely the person who’s there to fix it.

What breaks when DNS breaks

Here’s the part that scares dealers. When DNS breaks, the symptoms are confusing because they look like other problems.

• Who is our domain registrar? (GoDaddy, Namecheap, Network Solutions, etc.)
• Where is our DNS actually managed? (Sometimes the registrar. Sometimes Cloudflare, Microsoft, or your website host.)
• Who at our dealership, or at one of our vendors, has login access to change DNS records?
• When was the last time we changed anything in DNS?
• If our most technical person left tomorrow, who would know how to recover the domain?
  

The worst part: customers don’t see “DNS error.” They see a blank page, a spinning wheel, or a “this site can’t be reached” message. They don’t care what the cause was. They click back to Google and call the next dealership on the list.

What you should know without becoming an IT person

You’re not going to learn DNS. That’s fine. But there are five things you should be able to answer in under a minute:

If you can’t answer all five, that’s the gap. It’s not a “we should learn DNS” gap. It’s a “we should write this down and tell a couple of trusted people” gap.

The fix isn’t learning DNS. It’s owning the answer.

Here’s the part that matters. You do not need to manage DNS. You need to know who manages it, where the credentials live, and what to do if that person disappears. That’s a process problem, not a technology problem.

The dealerships that handle this well do three things:

• They keep DNS credentials in a documented, secure place — not in one person’s head.
• They review DNS access quarterly. Who has it? Do they still need it? When did they last use it?
• They require two-factor authentication on the registrar account. Full stop. This is the single biggest reason a domain gets stolen or hijacked.

The bottom line

DNS is the kind of thing that’s invisible until it isn’t. When it works, nobody thinks about it. When it breaks, it looks like every other tech problem, and it costs you leads, sales, and reputation before you figure out what’s going on.

You don’t need to be dangerous. You need to know who is — and make sure they’re accountable.

Next in the series: “What is a domain registrar, and what happens if we lose access to ours?”