DNS Lookup β Query Any Record Type for Any Domain Instantly
Learn how DNS works, what record types mean (A, MX, TXT, CNAME, NS), how to diagnose common DNS problems, and how to use a free DNS lookup tool to check any domain's records.
By sadiqbd Β· June 6, 2026
DNS is the internet's phone book β and when something's wrong with it, everything breaks
A website that doesn't resolve. An email that bounces immediately. A subdomain that never comes up. A CDN that isn't serving from the right edge. All of these can trace back to a DNS issue β a missing record, a misconfigured value, an outdated TTL, or a propagation delay after a recent change.
A DNS lookup tool queries the actual DNS infrastructure for any domain and record type, showing you exactly what's in DNS right now.
How DNS Works
The Domain Name System is a distributed, hierarchical database that maps human-readable domain names to IP addresses and other internet resource identifiers. When you type example.com in a browser:
- Your device checks its local DNS cache
- If not cached, it queries your configured DNS resolver (typically your ISP's or a public resolver like 8.8.8.8)
- The resolver asks the root DNS servers which nameservers are authoritative for
.com - Then asks those nameservers which are authoritative for
example.com - Then asks example.com's authoritative nameservers for the record you need
- The result is returned to your browser and cached for the record's TTL
This whole process typically takes 20β120 milliseconds on the first query, and is near-instant on subsequent queries when cached.
DNS Record Types
DNS stores different types of records for different purposes:
| Type | Purpose | Example |
|---|---|---|
| A | Maps domain to IPv4 address | example.com β 93.184.216.34 |
| AAAA | Maps domain to IPv6 address | example.com β 2606:2800:220:1:... |
| CNAME | Alias β points to another domain | www β example.com |
| MX | Mail exchanger β where email is delivered | mail.example.com, priority 10 |
| TXT | Text data β SPF, DKIM, DMARC, verification | v=spf1 include:... |
| NS | Nameservers β authoritative DNS servers | ns1.example.com |
| SOA | Start of Authority β zone metadata | Serial, refresh, retry, expire |
| PTR | Reverse DNS β IP to domain name | 93.184.216.34 β example.com |
| SRV | Service location | VoIP, XMPP, other services |
| CAA | Certificate Authority Authorization | Which CAs can issue SSL certs |
How to Use the DNS Lookup Tool on sadiqbd.com
- Enter the domain or hostname β e.g.
example.comormail.example.com - Select the record type β A, AAAA, MX, TXT, CNAME, NS, or All
- Run the lookup β the tool queries DNS and returns current records
- Read the results β IP addresses, mail servers, text records, TTL values, and more
Real-World Examples
Checking where a domain points
After migrating a website to a new server, you want to confirm DNS has propagated.
Lookup: example.com β A record
Result: 93.184.216.34 (new server IP)
If the result still shows the old IP, DNS hasn't propagated at all resolvers yet, or your TTL was set high and records are still cached.
Diagnosing email delivery failure
Emails to @example.com are bouncing with "no such domain" or similar errors.
Lookup: example.com β MX record
Result: No MX records found
Without MX records, mail servers don't know where to deliver email to your domain. Either the MX records were accidentally deleted or never configured. Add them through your DNS provider.
Verifying SPF record
Lookup: example.com β TXT record
Returns multiple TXT records. Look for the one starting with v=spf1:
v=spf1 include:_spf.google.com include:sendgrid.net ~all
This tells you which services are authorised to send email from this domain. If your new email marketing platform isn't listed, emails from it will fail SPF β add include:[provider] to the record.
Checking nameservers after domain transfer
After transferring a domain to a new registrar, you want to confirm the nameservers updated.
Lookup: example.com β NS record
Result: ns1.newdns.com, ns2.newdns.com β confirms nameserver delegation has updated.
Investigating a CNAME chain
A subdomain is slow or not resolving correctly.
Lookup: app.example.com β CNAME
Result: app.example.com β app.loadbalancer.provider.com β 198.51.100.42
The CNAME chain is visible β useful for understanding CDN or load balancer configurations and tracking down where a redirect might be going wrong.
TTL β Time to Live
Every DNS record has a TTL (Time to Live) measured in seconds. This is how long resolvers cache the record before re-querying. Common values:
| TTL | Meaning |
|---|---|
| 300 (5 min) | Changes propagate quickly β use before planned migrations |
| 3,600 (1 hour) | Standard for most records |
| 86,400 (24 hours) | Default for many providers β slow propagation after changes |
Before making DNS changes: reduce TTL to 300β600 seconds a day or two in advance. This ensures old cached records expire quickly after your change.
After changes are stable: increase TTL back to 3,600 or higher to reduce DNS query load.
DNS Propagation
After changing a DNS record, the new value doesn't appear everywhere instantly. It propagates as cached versions expire across resolvers globally. This can take anywhere from minutes (if old TTL was short) to 48 hours (if TTL was 86,400 and the record was recently queried).
During propagation:
- Some users see the old record; others see the new one
- This is normal and expected, not a sign of an error
- Propagation check tools (like the DNS lookup) can be queried against multiple nameservers to see the current state
Tips for Working With DNS
Lower TTL before planned changes. As mentioned above β do this 24β48 hours before any planned migration or record change.
Use the "All" record type to see the full DNS picture. A single query showing all record types for a domain saves multiple individual queries.
Check NS records first when debugging. If any other lookup fails unexpectedly, NS records tell you if you're querying the right authoritative nameserver.
Verify CAA records before requesting SSL certificates. If a CAA record is present and doesn't include your certificate authority, the CA will refuse to issue a certificate for that domain.
Frequently Asked Questions
Why does my DNS lookup show different results from what my registrar shows? There can be a propagation delay, or your registrar's admin panel shows what's been submitted while DNS shows what's live. Also, your DNS resolver may be returning a cached result β try querying against a different resolver (e.g. 8.8.8.8 for Google, 1.1.1.1 for Cloudflare).
What's the difference between a domain registrar and a DNS provider? A registrar manages domain registration (ownership). A DNS provider manages DNS records (routing). They're often the same service but don't have to be β many people register with GoDaddy but manage DNS through Cloudflare.
How do I find my domain's authoritative nameservers? Look up the NS records for your domain. The result lists the authoritative nameservers β the servers that hold the actual zone data for your domain.
Can I use public DNS (8.8.8.8) instead of my ISP's DNS? Yes. Public resolvers like Google (8.8.8.8) and Cloudflare (1.1.1.1) are often faster and more reliable than ISP resolvers. The DNS lookup tool typically queries multiple resolvers to show propagation state.
Is the DNS lookup tool free? Yes β completely free, no sign-up required.
DNS is the foundation that almost everything internet-based runs on. When something networking-related breaks, checking DNS records is almost always the first diagnostic step. The lookup tool gives you the current state of any domain's records in seconds.
Try the DNS Lookup tool free at sadiqbd.com β query any DNS record type for any domain instantly.