Home ›DNS Tools ›DNS Record Lookup

DNS Tool

DNS Record Lookup

Query DNS records for any domain. Fetch A, AAAA, CNAME, MX, NS, TXT, and SOA records instantly using Cloudflare's fast 1.1.1.1 resolver.

Coverage

All core DNS records

A, AAAA, CNAME, MX, TXT, NS, SOA in one query flow.

Best For

Pre/post migration validation

Verify source accuracy before investigating global cache delays.

How This Helps

DNS Lookup gives immediate configuration truth. Then combine with NS Lookup and Propagation Checker to isolate source errors vs resolver caching.

Core Use Cases

•Web routing: confirm A/AAAA/CNAME before launch.

•Email routing: validate MX + TXT before mailbox cutover.

•Authority checks: ensure NS/SOA reflect expected provider.

•Incident triage: quickly spot missing or stale values.

How to Use

Use DNS Record Lookup in 4 Steps

Enter domain

Type the domain you want to inspect (e.g. example.com).

Run lookup

Query DNS records through DNS-over-HTTPS for fast, reliable responses.

Review record groups

Inspect A/AAAA, CNAME, MX, TXT, NS and SOA records with values and TTLs.

Troubleshoot configuration

Compare expected values vs live values before or after DNS changes.

What is a DNS Lookup?

A DNS lookup queries DNS servers to retrieve live record data for a domain. It helps you verify web routing, mail routing, and authority at the same time.

For migrations and incident response, DNS lookup is the fastest first check because it tells you whether values are actually published before you assume propagation is broken.

💡DNS lookup answers: “What does this resolver return now?” If answers are mixed by region, pair this with a DNS propagation check.

DNS Record Types Reference

The table below covers all major DNS record types you will encounter when troubleshooting web routing, email delivery, security, and authority delegation:

Record	What it controls	Typical use case
A	Maps a hostname to an IPv4 address.	Website and app server routing.
AAAA	Maps a hostname to an IPv6 address.	IPv6-enabled servers and dual-stack deployments.
CNAME	Aliases one hostname to another canonical name.	CDN aliases, SaaS domain verification subdomains.
MX	Defines inbound mail servers with priorities.	Email routing, failover, and provider migration.
TXT	Stores arbitrary text values for policy and verification.	SPF, DMARC, DKIM selectors, Google/domain verification.
NS	Lists authoritative nameservers for the zone.	DNS provider migration and zone delegation.
SOA	Zone start-of-authority: serial, refresh, retry, TTL defaults.	Zone management and serial-number verification after changes.
PTR	Reverse lookup — maps IP address to hostname.	Mail server rDNS, spam filter trust, logging.
SRV	Specifies host, port, and priority for a service.	SIP, XMPP, Microsoft 365 Autodiscover, VoIP routing.
CAA	Restricts which certificate authorities can issue SSL certs.	SSL/TLS security policy enforcement.
DNSKEY	Stores public DNSSEC signing keys for the zone.	DNSSEC verification chain, zone signing.
DS	Delegation signer — links parent zone to child zone DNSSEC.	DNSSEC chain-of-trust delegation.
TLSA	Associates a TLS certificate with a domain via DNS (DANE).	DANE SMTP, certificate pinning in DNSSEC-signed zones.

Most day-to-day troubleshooting involves A, CNAME, MX, TXT, and NS records. DNSKEY, DS, and TLSA are relevant when diagnosing DNSSEC configuration issues.

Authoritative vs Recursive Answers

Authoritative nameservers hold the source zone data. Recursive resolvers (Google, Cloudflare, ISP DNS) cache answers for users. If you see mismatch, check both layers before acting.

Layer 1

Authoritative DNS

Best signal for whether the record is configured correctly at the source.

Layer 2

Recursive Resolver

Best signal for what real users currently experience from cached DNS.

When to Use DNS Lookup

Before cutovers: validate record values before switching traffic.
After updates: confirm live record values and TTL behavior.
Email debugging: verify MX and TXT records for authentication flow.
Outage triage: quickly detect wrong/missing records.

Practical Troubleshooting Workflow

Step 1: Query the target record in this DNS lookup tool.
Step 2: Verify NS authority using NS Lookup.
Step 3: Compare regions with DNS Propagation Checker.
Step 4: For mail issues, validate SPF/DMARC/DKIM from Email Tools.

CLI Examples (dig)

Use dig to query DNS records directly from your terminal. These commands cover the most common troubleshooting scenarios:

# A record — website routing

dig example.com A +short

# AAAA record — IPv6 address

dig example.com AAAA +short

# MX records — inbound email routing

dig example.com MX +short

# TXT records — SPF, DMARC, verification tokens

dig example.com TXT +short

# NS records — authoritative nameservers

dig example.com NS +short

# SOA record — zone serial and TTL defaults

dig example.com SOA +short

# CAA record — permitted certificate authorities

dig example.com CAA +short

# Query via a specific resolver (Cloudflare)

dig @1.1.1.1 example.com A +short

# Compare two resolvers side by side

dig @8.8.8.8 example.com A +short && dig @1.1.1.1 example.com A +short

# Query authoritative NS directly (bypass caches)

dig +trace example.com A

Use authoritative NS queries (+trace) when public resolver results conflict — correct authority with mixed public results indicates normal cache expiry, not a misconfiguration.

Frequently Asked Questions

What is a DNS lookup?

A DNS lookup is a query for DNS records (like A, AAAA, CNAME, MX, TXT, NS, or SOA) to learn how a domain is configured and where it should route traffic.

Why do DNS lookup results differ between tools?

Different tools may query different resolvers (Google, Cloudflare, ISP resolvers) and caches. TTL and DNS caching can cause temporary differences even when the authoritative zone is correct.

What is DNS-over-HTTPS (DoH)?

DNS-over-HTTPS sends DNS queries over HTTPS to a resolver. It helps prevent network interception and often works reliably from browsers and locked-down networks.

What record types should I check for email?

For email deliverability and anti-spoofing, check MX for inbound mail routing, and TXT records for SPF and DMARC. DKIM is usually a selector-based TXT record.

Can I use DNS lookup to troubleshoot propagation?

DNS lookup shows current answers from a resolver, but propagation issues are best diagnosed by comparing multiple regions/resolvers and verifying the authoritative nameserver responses.