What is a DNS record? A practical guide

The problem DNS solves

People remember names like getnetstats.com; computers route traffic using numeric IP addresses like 185.199.108.153. DNS — the Domain Name System — is the translation layer between the two. When you type a domain, your device asks DNS "what's the address for this name?" and DNS answers using a set of stored entries called records. Without it, you'd have to memorize IP addresses for every site you visit.

What a DNS record actually is

A DNS record is a single instruction stored in a domain's zone file, telling the internet one specific fact about that domain — where its website lives, where its email goes, who's allowed to send mail as it, and so on. Each record has a type (a short code like A or MX) that defines what kind of information it holds. A domain typically has many records working together.

The record types that matter

Here are the ones you'll actually encounter, in plain English:

• A record — maps the domain to its IPv4 address (the server it lives on). The most fundamental record; visiting a site starts here.
• AAAA record — the same thing for IPv6, the newer, larger address format. Many domains publish both.
• CNAME record — an alias that points one name at another (e.g., www.example.com → example.com). Useful so you only update the address in one place.
• MX record — mail exchange: names the servers that receive email for the domain, each with a priority (lower numbers tried first). No MX usually means the domain doesn't accept email.
• TXT record — free-form text, used in practice for domain verification and email-security policies (SPF, DKIM, DMARC) that control who's allowed to send mail as the domain. If you've ever "verified a domain" by pasting a code, that's a TXT record.
• NS record — name servers: the authoritative servers that actually hold the domain's records, usually run by its registrar or DNS host.

There are more (SOA, CAA, SRV, PTR), but those six cover the vast majority of what a domain needs.

TTL — why DNS doesn't update instantly

Every record carries a TTL (Time To Live) — a number, in seconds, telling other servers how long they're allowed to cache the answer before checking again. A TTL of 3600 means "remember this for an hour." TTL is why DNS feels slow to change: when you update a record, servers and devices that already cached the old value keep using it until their TTL expires. Lower TTLs update faster but mean more lookups; higher TTLs are more efficient but slower to change.

Propagation — the "it's not updated yet" feeling

When people say a DNS change is "propagating," they mean the world is gradually letting go of the old cached values as TTLs expire across countless resolvers. There's no single switch — different networks pick up the change at different times. A change can appear for you in minutes but take up to a day or two to be visible everywhere. This is completely normal, not a sign anything's broken — and it's why two DNS-checking tools can briefly disagree.

How to read your own records

You don't need command-line tools. You can look up any domain's live DNS records right here:

1. Enter the domain in the DNS Checker on GetNetStats.
2. You'll see its A, AAAA, MX, TXT, NS, and CNAME records as they currently resolve.
3. It runs in your browser via public DNS-over-HTTPS resolvers — nothing stored, no sign-up.

One honest note: a DNS lookup sends the domain you're checking to a public resolver (that's how every DNS query works, anywhere), and results reflect what that resolver currently has cached — so right after a change, give propagation time before assuming something's wrong.

Check a domain's records

Try it now with the DNS Checker — look up any domain and see exactly what its DNS says.