← All free resources

DNS Explained Without the Jargon (or the Panic)

If you’ve ever asked a web developer a simple question and gotten “oh, that’s a DNS thing” as the entire answer, you’ve been on the receiving end of one of tech’s favorite conversation-enders. DNS gets treated like arcane wizardry. It isn’t. It’s closer to a contact list, and once you see it that way, most of the mystery disappears.

The phonebook analogy actually works

Computers find each other using numbers (IP addresses), not names. Nobody wants to type a string of numbers to check their email, so DNS — the Domain Name System — exists to translate names humans use, like brashtechnology.com, into the numbers computers use.

That’s genuinely most of it. DNS is a distributed, public phonebook that maps names to numbers (and a few other useful facts), and every device on the internet checks that phonebook constantly, automatically, without you noticing.

The handful of record types you’ll actually encounter

You do not need to memorize a spec sheet. You need to recognize these when you see them, because they show up in every “how to set up X” guide you’ll ever follow:

• A record — points a domain (or subdomain) straight at an IP address. The most basic “this name means this server” entry.
• CNAME record — points a domain at another domain name instead of an IP address. Useful when a service you use manages its own servers and just wants you to alias to them.
• MX record — tells the internet where to deliver email for your domain. If this is wrong, mail for you either bounces or vanishes.
• TXT record — a free-text field used for verification and security, most commonly SPF, DKIM, and DMARC, which are what stop other people from convincingly forging email from your domain.

If you remember nothing else: MX decides where your mail goes, and TXT records are what keep other people from pretending to be you. Get an email deliverability problem, and 90% of the time the fix lives in one of those two.

“Propagation” is not magic, it’s caching

You’ve probably heard that DNS changes can “take 24-48 hours to propagate.” That sounds like the internet is slowly, mysteriously catching up. What’s really happening is much more mundane: every DNS record has a TTL (time to live) — a number that tells other computers how long they’re allowed to remember, or cache, the old answer before checking again.

If a record’s TTL is set to 24 hours, a change you make today might not be visible everywhere until that cache expires. That’s it. That’s the whole mystery. If you know you’re about to make a DNS change, you can often lower the TTL a day in advance so the eventual change takes effect in minutes instead of hours.

Why you should actually know where yours lives

You don’t need to become a DNS expert to run a small business. But you should be able to answer one question without calling anyone: where is my DNS managed, and can I log in and look at it myself?

If the answer is “I have no idea,” that’s worth fixing — not because you’ll spend your weekends tinkering with TXT records, but because DNS is the control panel for everything else: your website, your email, your subdomains, your verification for other tools. When something breaks, DNS is usually either the cause or the first place to check, and you want to be able to look.