Every website runs on DNS. When someone types your domain name into a browser, DNS (Domain Name System) translates that name into the server IP address where your site actually lives. It’s the phone book of the internet.
Most website owners never look at their DNS records until something breaks. Then it’s a scramble to figure out which record does what, whether it’s set correctly, and why emails stopped arriving or the site went down.
This guide teaches you how to look up DNS records for any domain, what each record type means, and how to spot and fix common problems.
How to Check DNS Records: 3 Methods
Method 1: DNS lookup tool (fastest)
Use a DNS lookup tool to check any domain instantly:
- Enter the domain name (e.g.,
example.com) - The tool queries the domain’s authoritative name servers
- View all DNS records: A, AAAA, CNAME, MX, TXT, NS, and more
This is the fastest way to see your complete DNS configuration without any technical setup.
Method 2: Command line (for developers)
If you prefer the terminal, use dig (macOS/Linux) or nslookup (all platforms):
# macOS / Linux
dig example.com ANY
# Check specific record type
dig example.com A
dig example.com MX
dig example.com TXT
# Windows Command Prompt
nslookup -type=ANY example.com
nslookup -type=MX example.comMethod 3: Domain registrar dashboard
Your domain registrar (GoDaddy, Namecheap, Cloudflare, etc.) has a DNS management panel where you can view and edit all records. Log in, find your domain, and look for “DNS Settings” or “DNS Management.”
Which method to use:
- Quick check of any domain → DNS lookup tool
- Debugging with full technical output → command line
- Editing your own records → domain registrar dashboard
Every DNS Record Type Explained
Here’s what each DNS record does, when you need it, and what a typical value looks like:
The Essential Records (Every Website Needs These)
| Record | Name | What It Does | Example Value |
|---|---|---|---|
| A | Address | Maps your domain to an IPv4 address (your server’s location) | 93.184.216.34 |
| AAAA | IPv6 Address | Maps your domain to an IPv6 address (modern internet protocol) | 2606:2800:220:1::248 |
| NS | Name Server | Points to the DNS servers that manage your domain’s records | ns1.cloudflare.com |
Website Routing Records
| Record | Name | What It Does | Example Value |
|---|---|---|---|
| CNAME | Canonical Name | Creates an alias pointing one domain to another domain | www → example.com |
| SOA | Start of Authority | Administrative info: primary server, admin email, zone serial number | ns1.example.com admin.example.com |
| PTR | Pointer | Reverse DNS: maps an IP address back to a domain name | 93.184.216.34 → example.com |
Email Records
| Record | Name | What It Does | Example Value |
|---|---|---|---|
| MX | Mail Exchange | Routes incoming email to the correct mail server | 10 aspmx.l.google.com |
| TXT (SPF) | Sender Policy | Specifies which servers can send email from your domain | v=spf1 include:_spf.google.com ~all |
| TXT (DKIM) | Email Signing | Cryptographic signature proving emails are authentic | v=DKIM1; k=rsa; p=MIGfMA0… |
| TXT (DMARC) | Email Policy | Tells receiving servers what to do with emails that fail SPF/DKIM | v=DMARC1; p=quarantine; rua=mailto:… |
Verification and Service Records
| Record | Name | What It Does | Common Use |
|---|---|---|---|
| TXT | Text | Stores arbitrary text for verification and policies | Google Search Console verification, domain ownership |
| SRV | Service | Defines location of specific services (port, weight, priority) | VoIP, Microsoft 365, SIP protocols |
| CAA | Certificate Authority | Specifies which CAs can issue SSL certificates for your domain | SSL/TLS security policy |
How DNS Records Work Together: A Real-World Example
When someone visits your website and sends you an email, multiple DNS records work together. Here’s what happens behind the scenes:
Understanding TTL (Time to Live)
Every DNS record has a TTL value measured in seconds. It tells DNS resolvers how long to cache the record before checking for updates.
| TTL Value | Duration | When to Use |
|---|---|---|
| 300 | 5 minutes | Before or during DNS changes (fast propagation) |
| 3600 | 1 hour | Standard for most records (good balance) |
| 14400 | 4 hours | Stable records that rarely change |
| 86400 | 24 hours | NS records and very stable configurations |
Pro tip for DNS migrations: Before changing DNS records (like moving to a new host), lower your TTL to 300 seconds 24-48 hours in advance. This ensures the old TTL expires, so when you make the actual change, it propagates quickly. After the migration is complete and verified, raise the TTL back to a normal value.
Common DNS Problems and How to Fix Them
Website not loading
Symptoms: Browser shows “This site can’t be reached” or “DNS_PROBE_FINISHED_NXDOMAIN”
Check: Run a DNS lookup for your domain and verify the A record points to the correct IP address.
Common causes:
- A record points to an old server IP after migration
- Nameservers haven’t been updated at the registrar
- Domain expired (check with a WHOIS lookup)
- DNS propagation still in progress after recent changes
Emails not being delivered
Symptoms: Emails bounce, go to spam, or never arrive
Check: Look up your MX records and TXT records (SPF, DKIM, DMARC).
Common causes:
- MX records point to the wrong mail server
- Missing SPF record (receiving servers can’t verify your sending authority)
- Missing or incorrect DKIM record (emails fail signature verification)
- No DMARC record (no policy for handling failed authentication)
www version not working
Symptoms: example.com loads but www.example.com doesn’t (or vice versa)
Check: Verify you have either a CNAME record for www pointing to your root domain, or a separate A record for www.
Common causes:
- Missing CNAME record for
wwwsubdomain - CNAME points to the wrong domain
- SSL certificate doesn’t cover the
wwwvariant (check with an SSL certificate checker)
Slow DNS resolution
Symptoms: Website takes longer than usual to start loading
Check: Look at your TTL values and NS records.
Common causes:
- NS records point to slow or overloaded name servers
- TTL values are too low (causing excessive DNS queries)
- Too many DNS records creating large zone files
DNS Records and SEO: What Matters
DNS configuration affects your website’s SEO in several ways:
-
Site speed: DNS resolution adds 50-200ms to every page load. Fast, reliable name servers reduce this. CDN providers like Cloudflare and Vercel have some of the fastest DNS resolution times.
-
Uptime and availability: If your DNS goes down, your entire website goes down. Use at least two NS records pointing to different name servers for redundancy.
-
www vs non-www: Pick one canonical version and redirect the other. Inconsistent handling splits your SEO authority between two URLs. Your DNS setup (A record vs CNAME for www) determines how this works.
-
Email deliverability: SPF, DKIM, and DMARC records are TXT records in your DNS. Without them, your outreach emails and contact form notifications may land in spam.
-
SSL/HTTPS: Your DNS configuration determines how SSL certificates are validated. CAA records specify which certificate authorities can issue certificates for your domain.
DNS Records Checklist
Use this to verify your DNS configuration is complete:
Next Steps
- Look up your DNS records now with our DNS Lookup Tool
- Check domain ownership with our WHOIS Domain Lookup
- Verify your SSL certificate with our SSL Certificate Checker
- Test your robots.txt to make sure crawlers can access your site properly
- Check your sitemap with our Sitemap Checker
- Audit your full SEO setup including DNS, schema, and more with our SEO services
Frequently Asked Questions
How do I check my website's DNS records?
What is an A record in DNS?
What is the difference between A and CNAME records?
What are MX records and why do they matter?
What are TXT records used for?
How long does it take for DNS changes to take effect?
What does TTL mean in DNS records?
Why is my website not loading after changing DNS records?
Check Your DNS Records Now
Look up A, AAAA, CNAME, MX, TXT, NS, and more for any domain. Free, instant results.
