How to Check DNS Records for Any Domain
When a domain doesn't resolve the way you expect — email not arriving, a subdomain not pointing where it should, a site not loading after you changed hosts — the answer almost always lives in DNS records. This guide covers the main record types, what each one does, and how to check them for any domain.
What Are DNS Records?
DNS (Domain Name System) records are instructions stored on nameservers that tell the internet how to handle requests for a domain — which server hosts the website, which servers handle email, and how various subdomains and services are configured. Every domain has a set of these records, and misconfigured ones are one of the most common causes of "my site/email isn't working" problems.
The Main DNS Record Types
| Record | Purpose |
|---|---|
| A | Points a domain to an IPv4 address (the most common record — this is what makes a website load) |
| AAAA | Same as A, but for IPv6 addresses |
| CNAME | Points a subdomain to another domain name (an alias) instead of directly to an IP |
| MX | Specifies which mail servers handle email for the domain, with a priority order |
| TXT | Stores arbitrary text, commonly used for domain verification and email authentication (SPF, DKIM, DMARC) |
| NS | Specifies which nameservers are authoritative for the domain |
| SOA | Start of Authority — contains administrative info about the domain's DNS zone |
| SRV | Specifies a host and port for specific services (e.g. VoIP, some chat protocols) |
Why Email Problems Are Usually DNS Problems
Email deliverability issues are one of the most common reasons to check DNS records. If MX records point to the wrong mail server, email simply won't arrive. If SPF, DKIM, or DMARC TXT records are missing or misconfigured, your outgoing email is more likely to be marked as spam by receiving servers — these three records together tell receiving mail servers that your email is legitimately coming from your domain and hasn't been tampered with.
How to Check DNS Records
- Open the DNS Records Checker
- Enter the domain you want to check
- View all record types (A, AAAA, CNAME, MX, TXT, NS, and more) in one place
- Compare against what you expect to confirm your DNS is configured correctly
DNS Propagation: Why Changes Take Time
DNS records are cached at multiple levels — your ISP, your operating system, and various resolvers around the world — for a duration set by the record's TTL (Time To Live). This means after you change a DNS record, it can take anywhere from a few minutes to 48 hours for the change to be visible everywhere, depending on the TTL and how aggressively different resolvers cache. If you're about to make a DNS change and want faster propagation afterward, lower the TTL a day or two in advance.
Why DNS Changes Take Time to Propagate (TTL Explained)
Every DNS record has a TTL (Time To Live) value, measured in seconds, which tells other DNS servers how long they're allowed to cache that record before re-checking it. This is why a DNS change — like pointing your A record to a new hosting server — doesn't take effect everywhere instantly. Servers and ISPs that already cached your old record with a 24-hour TTL will keep serving the old value for up to 24 hours after you make the change, even though the authoritative record has already updated. A common practice before a planned migration is to lower the TTL (to something like 300 seconds) a day or two in advance, so that when the actual change happens, it propagates much faster since caches expire sooner.
Basic DNS Troubleshooting Steps
- Check the record at the authoritative source first — look up the record directly rather than assuming what you configured is what's actually live, since a typo or an unsaved change is a common culprit.
- Check from multiple locations — because of caching and regional DNS servers, a change can appear live in one location and not yet in another. Checking from a tool that queries multiple public DNS servers helps distinguish "not propagated yet" from "actually misconfigured."
- Verify you're editing the right zone — if a domain's nameservers were recently changed (e.g. moved to a new registrar or DNS provider), edits made in the old provider's dashboard won't have any effect, since that zone is no longer authoritative.
Frequently Asked Questions
Why does my domain show different results from different locations?
This is usually DNS propagation in progress — different DNS resolvers around the world update their cached records at different times after a change. It should resolve consistently everywhere once the TTL expires and all resolvers refresh their cache.
What's the difference between an A record and a CNAME?
An A record points directly to an IP address. A CNAME points to another domain name, which itself must eventually resolve to an IP through its own A record. CNAMEs are useful for subdomains that should always match another domain's current IP without needing manual updates.
Do I need SPF, DKIM, and DMARC records?
If your domain sends any email, yes — these significantly improve deliverability and reduce the chance of your email landing in spam folders. Most email providers (Google Workspace, Microsoft 365, etc.) provide the exact TXT record values to add during setup.
Related Guides
- What Is My IP Address? Public vs Private IP Explained
- HTTP Status Codes Explained: 200, 301, 404 and What They Mean
- The Complete Guide to Free Online Tools (all tool guides)
Try it yourself: Use our free Find DNS Records →
What's your reaction?
Written by
JayDev is an independent developer who builds and maintains SEO Stack Tools. Tool descriptions and blog content are drafted with AI assistance, then reviewed and edited by JayDev for accuracy before publishing. Questions or corrections go straight through the Contact page.
