What Is a DNS Lookup?
A DNS lookup (also called a DNS check or DNS query) is the process of querying the Domain Name System to retrieve records associated with a specific domain name. Every time you visit a website, send an email, or use an online service, your device performs DNS lookups behind the scenes — translating human-readable domain names like example.com into machine-readable IP addresses like 93.184.216.34.
Our free online DNS lookup tool lets you manually query those same records — without needing to open a terminal or run nslookup commands. Just enter a domain name, choose a record type (or check all records at once), and get results instantly from live DNS nameservers.
This is especially useful for developers, sysadmins, and anyone managing a website or domain — whether you're verifying a new DNS configuration, debugging email delivery problems, checking nameserver delegation, or confirming that DNS changes have propagated globally.
DNS Record Types – Detailed Guide
A Record (IPv4 Address)
The most fundamental DNS record. An A record maps a domain name to an IPv4 address. When you check the A record for a domain, you're finding out which web server that domain points to. Multiple A records can exist for the same domain for load balancing or redundancy.
When to check it: Website not loading, verifying hosting IP, confirming CDN configuration, or after changing hosting providers.
AAAA Record (IPv6 Address)
The IPv6 equivalent of the A record. As the internet transitions toward IPv6 addressing, AAAA records are increasingly important. An AAAA record maps a domain to a 128-bit IPv6 address.
When to check it: Testing IPv6 connectivity, verifying dual-stack (IPv4 + IPv6) configuration, or debugging issues on IPv6 networks.
MX Record (Mail Exchange)
MX records tell the internet which mail servers accept incoming emails for a domain. Each MX record has a priority number — lower numbers mean higher priority. If the primary mail server is unreachable, email is routed to a backup server with a higher priority number.
When to check it: Emails not delivering, migrating to a new email provider (Google Workspace, Microsoft 365, Zoho), verifying mail server configuration.
NS Record (Nameserver)
NS records (nameserver records) specify which DNS servers are authoritative for a domain — meaning which servers hold the master copy of that domain's DNS zone. A domain typically has two or more nameservers for redundancy.
When to check it: After transferring a domain to a new registrar, setting up custom nameservers with a DNS provider (Cloudflare, Route 53, etc.), or troubleshooting DNS resolution failures.
TXT Record (Text)
TXT records store arbitrary text data in DNS and are heavily used for domain verification and email security. The three most important TXT-based standards are:
- SPF (Sender Policy Framework): Lists authorized mail servers to send email on behalf of your domain — prevents spoofing.
- DKIM (DomainKeys Identified Mail): Provides a cryptographic signature to verify email authenticity.
- DMARC (Domain-based Message Authentication): Combines SPF and DKIM to define policy for handling emails that fail authentication.
When to check it: Emails landing in spam, setting up Google Search Console, verifying domain ownership for third-party services, checking SPF/DKIM/DMARC configuration.
CNAME Record (Canonical Name / Alias)
A CNAME record creates an alias from one domain name to another. For example, www.example.com can be a CNAME pointing to example.com. When DNS resolves a CNAME, it follows the chain until it finds an A or AAAA record.
When to check it: Configuring subdomains (blog, shop, app), setting up CDN integrations, troubleshooting redirect chains, or verifying SaaS service custom domain setup.
SOA Record (Start of Authority)
The SOA record is mandatory for every DNS zone and contains administrative information: the primary nameserver, the administrator's email, and timing parameters like the zone serial number, refresh interval, retry interval, expiry time, and minimum TTL.
When to check it: Advanced DNS zone troubleshooting, verifying DNS replication between primary and secondary nameservers, checking zone serial numbers after DNS updates.
DNS Propagation – Why Changes Take Time
When you update a DNS record, the change doesn't take effect instantly everywhere. DNS propagation is the time it takes for updated records to spread across all DNS resolvers and caches around the world. Here's what controls that timing:
TTL (Time to Live)
Every DNS record has a TTL value — a number in seconds that tells resolvers how long to cache the record before fetching a fresh copy. A TTL of 3600 means resolvers cache the record for 1 hour. A TTL of 300 (5 minutes) means changes propagate much faster.
Typical Propagation Times
- Fast (under 15 min): If TTL was already set low before the change
- Standard (1–4 hours): Most common scenario with moderate TTL values
- Slow (up to 48 hours): When previous TTL was very high (86400 = 24 hours) or registrar propagation is slow
Pro tip: Before making DNS changes (especially domain migrations), lower your TTL to 300 seconds at least 24 hours in advance. This minimizes propagation delay when you make the actual change. After migration is confirmed stable, raise the TTL back to a normal value like 3600 or higher.
How to Check DNS Records – Multiple Methods
There are several ways to perform a DNS lookup. Each has its own advantages:
✅ Method 1: Online DNS Lookup Tool (This Page)
The easiest method — no installation or technical knowledge required. Enter the domain, select the record type, and get results instantly. Perfect for quick checks and sharing results with your team. Our tool queries live nameservers directly, so you always get current data.
🖥️ Method 2: nslookup Command (Windows / Mac / Linux)
Built into all major operating systems. Open a terminal or command prompt and run:
$ nslookup example.com
$ nslookup -type=MX example.com
$ nslookup -type=TXT example.com 8.8.8.8
🔧 Method 3: dig Command (Linux / Mac)
The dig (Domain Information Groper) command is the preferred tool for sysadmins — it provides more detail than nslookup:
$ dig example.com
$ dig MX example.com
$ dig ANY example.com +noall +answer
🌍 Method 4: Public DNS Resolvers
You can query specific public DNS resolvers to check how a domain resolves from different networks. Common resolvers include Google (8.8.8.8), Cloudflare (1.1.1.1), and OpenDNS (208.67.222.222). This is useful for comparing propagation status across different regions.
DNS Troubleshooting Guide
❌ Problem: Website shows old IP / not loading after migration
Fix: Check the A record — does it show the new IP? If yes, the change propagated. If your browser still shows the old site, clear your browser DNS cache or try from a different network. DNS changes may have propagated globally but your local resolver is still caching the old value.
❌ Problem: Emails not being received
Fix: Look up MX records for the domain. Verify the mail server hostnames and priority values match what your email provider specifies. Then check that those mail server hostnames also have valid A records pointing to the correct IPs.
❌ Problem: Emails going to spam
Fix: Check TXT records for SPF, DKIM, and DMARC. A missing SPF record is one of the most common causes of legitimate email being flagged as spam. Use our tool to look up TXT records and verify these are properly configured.
❌ Problem: Subdomain not resolving
Fix: Check if there's a CNAME or A record for that specific subdomain. Subdomains require their own DNS records — a root domain's A record doesn't automatically apply to subdomains unless a wildcard record (*.example.com) is configured.
❌ Problem: Domain resolves differently in different locations
Fix: This is usually DNS propagation in progress. Check NS records to confirm the authoritative nameservers are correct. If you changed nameservers recently, give it up to 48 hours. You can use our tool alongside a propagation checker to see status from multiple geographic locations.
Frequently Asked Questions
What is the difference between a DNS lookup and a WHOIS lookup?
A DNS lookup retrieves technical records that control how a domain functions — where it points, which mail servers handle email, and what security policies apply. A WHOIS lookup retrieves domain registration information — who registered the domain, when it expires, and who the registrar is. Both are useful but serve different purposes.
How long does DNS propagation take?
DNS propagation can take anywhere from a few minutes to 48 hours. The actual time depends on the TTL (Time to Live) of the record being changed. Records with a TTL of 300 seconds (5 minutes) propagate within minutes. Records with a TTL of 86400 seconds (24 hours) can take up to 48 hours to fully propagate worldwide.
Is this DNS lookup tool free to use?
Yes, our DNS lookup tool is completely free with no limits on queries. No account or registration is required. We do not log or store the domains you look up.
What is the difference between nslookup and dig?
Both are command-line DNS lookup tools. nslookup is available on Windows, Mac, and Linux — simpler syntax, good for quick checks. dig (Linux/Mac) provides more detailed output including query timing, answer sections, and authority records, making it the preferred tool for in-depth DNS diagnostics.
Why do I see different DNS results from different locations?
DNS propagation is not instant — different DNS resolvers around the world cache records for the duration of the TTL. After a DNS change, resolvers with the old record cached will return old results until the cache expires. This is normal and expected; wait for the TTL to expire and the new values will propagate fully.
What does "DNS zone check" mean?
A DNS zone check is a comprehensive review of all DNS records for a domain — verifying that A, MX, NS, TXT, and other records are correctly configured and consistent across authoritative nameservers. It's often done before domain migrations, after configuration changes, or as part of a security audit.
How do I check nameservers for a domain?
Select "NS" as the record type in our DNS lookup tool and enter your domain. The results will show all authoritative nameservers for that domain. You can verify these match what's set at your domain registrar. Nameserver mismatches are a common cause of DNS resolution failures after domain transfers.