Why you need an independent DNS check
When you run nslookup or dig on your own machine, you're querying through your ISP's resolver — and that resolver caches results. If a DNS record changed an hour ago, your local machine might still be returning the old value for another 23 hours depending on the TTL. That stale cache is invisible to you unless you check from somewhere else.
An independent DNS lookup tool queries the authoritative nameservers directly, bypassing any intermediary cache. What you get back is the current published record — exactly what a new visitor or a mail server in another region would see. This is the check that matters when you've just updated a record and need to confirm it's live.
DNS record types explained
A records map a domain to an IPv4 address — the most common lookup. AAAA records do the same for IPv6. CNAME records are aliases: they point one hostname to another, so www.example.com can point to example.com without duplicating the A record.
MX records specify which servers handle email for a domain, each with a numeric priority (lower number = higher priority). TXT records carry text strings used for SPF, DKIM, DMARC, and domain ownership verification. NS records name the authoritative nameservers for the domain. The TTL (time to live) on each record tells resolvers how many seconds to cache the result before re-querying.
How to check DNS records
Go to the DNS lookup tool, enter the domain name you want to query, and choose the record type from the dropdown. Click Lookup. The tool queries authoritative nameservers and returns whatever records are currently published — along with each record's TTL.
To check all record types at once, select "ANY" from the record type list. Note that some nameserver configurations restrict ANY queries; if you get no results, query each type individually. For email troubleshooting, query MX and TXT in separate lookups to see both mail routing and SPF/DKIM configuration clearly.
Reading the results
Each result row shows the record type, its value, and the TTL in seconds. A TTL of 3600 means the record will be cached for one hour by downstream resolvers before they re-check. If you just changed a record with a 86400-second TTL, it could take up to 24 hours to propagate fully — though most resolvers will pick it up in under an hour.
For MX records, pay attention to priority numbers. If you have two MX records with priorities 10 and 20, mail servers try the priority-10 server first and fall back to priority-20 only if the first is unreachable. Multiple MX records with the same priority number get round-robin treatment.
Common use cases
Confirming a domain migration went through: query the A record and verify it resolves to the new server IP. Debugging email delivery problems: check MX records to see if they point to the right mail server, then check TXT records to confirm your SPF record is published correctly using the SPF checker.
Verifying a subdomain setup after adding a CNAME in your registrar's DNS panel. Checking that DMARC policy is in place before a mail authentication audit with the DMARC checker. Confirming NS records after transferring a domain to a new registrar. Any of these checks from your local machine risks reading a cached result — do them from an independent tool.
Getting a clean DNS picture
The combination of A, MX, TXT, and NS lookups gives you a complete picture of how a domain is configured. For registrar and ownership information, the WHOIS lookup shows registration dates, expiry, and the current registrar on record.
DNS problems are almost always simpler than they look: a typo in a value, a record pointing to the wrong server, a TTL that hasn't expired yet. An accurate lookup from an independent server tells you which of those it is in seconds.