DNS Lookup - Query DNS Records Online Free

About This Tool

Query DNS records for any domain in seconds with this free DNS lookup tool. Enter a domain name, pick a record type, and instantly see the authoritative DNS data returned by public resolvers. This tool supports A, AAAA, MX, TXT, CNAME, NS, and SOA record types, displays full response details including TTL values and response times, and provides the raw JSON output for technical analysis. DNS (Domain Name System) is the backbone of the internet, translating human-readable domain names into machine-readable IP addresses and routing information. Every time you visit a website, send an email, or connect to an online service, DNS resolution happens behind the scenes. Understanding DNS records is critical for system administrators, web developers, email deliverability specialists, and anyone managing domain configurations. This tool provides accurate, up-to-date results by querying trusted public resolvers. Your queries stay private, and you get the same resolution data that billions of internet users rely on daily. Use it to verify domain configurations, troubleshoot email delivery issues, check propagation after DNS changes, or audit a domain's public DNS footprint.

Understanding DNS Record Types

Each DNS record type serves a specific purpose in domain configuration:

A Records map a domain to an IPv4 address (e.g., 93.184.216.34). This is the most common record type and tells browsers where to find a website.
AAAA Records map a domain to an IPv6 address. As IPv4 addresses run out, more sites rely on AAAA records for next-generation connectivity.
MX Records specify which mail servers accept email for a domain. The priority value determines the order servers are tried.
TXT Records hold arbitrary text data, commonly used for email authentication (SPF, DKIM, DMARC), domain verification, and security policies.
CNAME Records create an alias from one domain to another. For example, www.example.com might be a CNAME pointing to example.com.
NS Records identify the authoritative nameservers for a domain, telling the DNS system where to find definitive records.
SOA Records contain administrative metadata including the primary nameserver, contact email, serial number, and refresh intervals.

How to Read TTL Values

TTL (Time to Live) is measured in seconds and tells DNS resolvers how long to cache a record before requesting fresh data. A TTL of 300 means the record is cached for 5 minutes. Short TTLs (60-300 seconds) allow rapid changes but increase DNS query load. Long TTLs (3600-86400 seconds) reduce query traffic but delay propagation of changes. When planning a DNS migration, lower TTLs beforehand so changes propagate faster once you switch. After migration, raise TTLs back to reduce resolver load.

Troubleshooting Email Delivery with MX Records

MX records are the first thing to check when diagnosing email delivery failures. Each MX record has a priority value (lower is preferred). If your primary mail server at priority 10 is unreachable, senders will try the backup at priority 20. Common issues include missing MX records entirely (email bounces), MX records pointing to non-existent servers, and mismatched SPF/DKIM TXT records that cause email to land in spam. Querying all three record types (MX, TXT for SPF, and TXT for DKIM) gives a complete picture of your email configuration.

DNS Propagation and Caching

After updating DNS records, changes do not take effect instantly worldwide. DNS resolvers cache records based on their TTL value, and some ISP resolvers may cache aggressively beyond the stated TTL. Full propagation typically takes 1-48 hours depending on the old TTL values and resolver behavior. Use this tool to query Google Public DNS, which respects TTL values accurately, and compare with your local resolver to spot propagation delays. If Google shows the new records but your browser still shows old content, your local ISP resolver or browser DNS cache may be stale.

Frequently Asked Questions

Why do I see different DNS results than expected?

Several factors can cause unexpected DNS results. Caching at various levels (browser, OS, ISP resolver) may show stale records. Your DNS provider may not have finished publishing changes. CNAME flattening by some providers can change how records appear. Additionally, GeoDNS configurations return different IP addresses depending on the querying resolver's location. This tool queries Google Public DNS from their infrastructure, which may differ from your local resolver's view.

What does NXDOMAIN mean in DNS responses?

NXDOMAIN (Non-Existent Domain) means the queried domain name does not exist in DNS at all. This is different from getting zero records for a valid domain. NXDOMAIN indicates the domain has never been registered, has expired, or the authoritative nameserver explicitly declares it nonexistent. If you see NXDOMAIN for a domain you own, check that your domain registration is active and your nameservers are correctly configured at your registrar.

How do I verify my SPF and DKIM records?

SPF and DKIM records are stored as TXT record types. Select "TXT" as the record type and query your domain. SPF records start with "v=spf1" and define which servers can send email on your behalf. DKIM records are stored at a specific selector subdomain (e.g., selector1._domainkey.example.com). For DMARC, query "_dmarc.example.com" as a TXT record. Each of these authentication methods helps prevent email spoofing and improves deliverability.

Can I query DNS records for subdomains?

Yes. Enter the full subdomain in the domain field (e.g., blog.example.com or mail.example.com). Subdomains can have their own A, AAAA, CNAME, MX, and TXT records independent of the parent domain. This is useful for verifying CDN configurations (often CNAME records), checking subdomain email routing, or confirming that development/staging subdomains resolve correctly.

What is the difference between NS and SOA records?

NS (Name Server) records list the authoritative DNS servers for a domain. These are the servers that hold the definitive copy of your DNS records. SOA (Start of Authority) records contain administrative information about the DNS zone, including the primary nameserver, the responsible party's email address, a serial number that increments with each change, and timing parameters for zone transfers between primary and secondary nameservers. NS records tell resolvers where to ask; SOA records describe how the zone is managed.