You point a new domain at a server, or you move to a new host, and the browser greets you with “Server Not Found.” Half your links are dead and your inbox fills with “is the site down?” messages. Before you touch anything else, run a DNS lookup. It takes ten seconds and tells you whether the problem lives in your DNS or somewhere else entirely.
DNS is the internet’s phonebook. People remember names like example.com, but machines talk to each other using IP addresses. DNS translates one into the other. When that translation fails or returns stale data, everything built on top of it fails too: websites, email, SSL certificates, and third-party verifications. That’s why checking it is always step one.
What a DNS Lookup Actually Does
When you type a domain into a browser, a chain of servers answers the question “where does this name live?” Here’s the path, in plain terms:
- Recursive resolver. Usually run by your ISP, or by a public service like Google or Cloudflare. It does the legwork on your behalf and remembers answers for a while.
- Root servers. They don’t know the answer, but they know who handles each ending, like .com or .org.
- TLD servers. The servers for .com (or whatever the extension is) point the resolver to the domain’s own nameservers.
- Authoritative nameservers. The final stop. These hold the real records and give the definitive answer.
The resolver then caches that answer for as long as the record’s TTL (time to live) allows. That cache is the reason changes don’t appear instantly, and we’ll come back to it.
Core DNS Record Types
Every DNS lookup returns one or more of these record types:
| Record Type | What It Resolves | Common Real-World Example |
|---|---|---|
| A | A name to an IPv4 address | Pointing your domain to a Hostinger server IP |
| AAAA | A name to an IPv6 address | Same site, reachable over IPv6 |
| CNAME | One name as an alias of another name | Pointing www to shops.myshopify.com for a Shopify store |
| MX | The mail servers that accept email for the domain | Google Workspace mail routing |
| TXT | Free-form text, used for verification and email authentication | Google Workspace domain verification, SPF, DKIM, DMARC |
| NS | The authoritative nameservers for the domain | Switching DNS management to Cloudflare |
| SOA | Administrative details about the zone, such as the serial number | Used by secondary nameservers to know when to sync |
One rule worth remembering: a CNAME can’t sit on the root of a domain alongside other records, so root domains usually use A records. An a record cname lookup is often how you spot the mistake when www works but the bare domain doesn’t.
How to Run a DNS Lookup
You have two options, and good admins use both.
Web-based inspection. A browser-based dns lookup tool is the fastest way to check DNS records, especially for non-technical teammates. Type the domain, pick a record type, and read the answer. Many also let you query from several locations around the world, which doubles as a dns propagation check.
Command-line utilities. Faster for repeat work and available on every machine. Two commands cover almost everything:
nslookup example.com
nslookup -type=MX example.com
dig example.com A
dig example.com MX +short
dig @8.8.8.8 example.comThe nslookup command ships with Windows, macOS, and most Linux systems. dig gives richer output, including TTL values and how long the query took. The last line asks Google’s public resolver directly, which is a quick way to compare its answer with your own.
How Outreach Teams Use a DNS Lookup Audit
Operations that depend on email deliverability and live partner sites run into DNS problems constantly. Professional digital PR and link-building agencies, such as Links Builder Hub, use regular dns lookup audits as part of their infrastructure checks. The typical checks look like this:
- Sender domain authentication. Confirm that MX records exist and that the SPF, DKIM, and DMARC TXT records are published and correct. Cold outreach from a domain with missing or broken authentication lands in spam, and that kills reply rates quietly.
- Partner publisher domains. Before a placement goes live, make sure the publisher’s domain resolves consistently, with no expired nameservers or intermittent failures that could take the page offline.
- Client landing pages. Verify that target pages resolve quickly and correctly. The
Query timeline indigoutput gives a rough idea of resolution speed.
It’s a routine hygiene check, similar to a pilot’s checklist: boring, quick, and far cheaper than debugging a failed campaign.
Troubleshooting a Failed DNS Lookup
DNS Propagation Delays and TTL
“Propagation” is a slightly misleading word. Nothing travels around the internet. Resolvers around the world simply keep the old answer until its TTL expires. If your record had a TTL of 86400 seconds (24 hours), some users will see the old server for up to a day after you change it. Changes to nameservers at the registrar can take even longer, often up to 48 hours.
When you suspect a delay, run a dns lookup directly against your authoritative nameserver. If that answer is correct and others still show the old one, you’re just waiting for caches to expire. If the authoritative answer is wrong, the fix is in your DNS panel.
NXDOMAIN vs. SERVFAIL
These two errors look similar but mean different things:
- NXDOMAIN means the name doesn’t exist. Check for a typo, an expired domain, or a missing record for that specific subdomain.
- SERVFAIL means the resolver couldn’t get a valid answer. Common causes are a nameserver that’s down or misconfigured, a broken delegation at the registrar, or a failed DNSSEC validation.
Stale Local DNS Cache
Sometimes the internet is fine and your own computer is stuck on an old answer. A dns lookup from your own machine can show cached data, even after the record has been fixed. Flush it:
Windows: ipconfig /flushdns
macOS: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
Linux: resolvectl flush-cachesThen retry. If your browser still disagrees, restart it or try a private window, since browsers keep their own DNS cache too.
Conclusion
Most “the site is down” panics are DNS problems in disguise, and a quick dns lookup answers the question before anyone starts guessing. The best habit is preparation: about 48 hours before a migration, lower your TTL to 300 seconds (5 minutes), make the move, verify the new records, and then raise the TTL back to a sensible value like an hour or more. That small change turns a risky cutover into a controlled one.

Pingback: Epoch Converter: Unix Timestamps Made Readable