DNS Query Tool
Full Domain Name System (DNS) query with answer, authority, and additional sections.
Monitor DNS Query Tool automatically
Full Domain Name System (DNS) query with answer, authority, and additional sections. NetTests can run this check on a schedule, preserve historical results, compare changes over time, and alert you the moment something breaks.
Start monitoring free → See all monitoring productsFrequently Asked Questions
What makes dig different from nslookup, host, or drill?
dig is the tool most network engineers reach for first because it shows the complete response a nameserver sent — the ANSWER section plus the AUTHORITY and ADDITIONAL sections most other tools hide. That extra detail makes it the standard choice for debugging delegation and referral problems, not just reading back a single record.
How do I read dig's ANSWER, AUTHORITY, and ADDITIONAL sections?
ANSWER holds the record(s) that actually answer your query. AUTHORITY lists the nameservers considered authoritative for the zone — useful for spotting a stale or misconfigured delegation. ADDITIONAL supplies extra records the resolver included to save you a follow-up query, most often the IP addresses of nameservers named in AUTHORITY. A referral with an empty ANSWER but a populated AUTHORITY section usually means you're querying the wrong nameserver for that name.
What DNS record types should I know?
- A — IPv4 address of the domain.
- AAAA — IPv6 address.
- CNAME — alias pointing to another hostname.
- MX — mail server(s) for the domain.
- TXT — free-text records; used for SPF, DKIM, domain verification.
- NS — nameservers authoritative for the domain.
- SOA — start-of-authority; holds the primary NS and serial number.
- PTR — reverse DNS; maps an IP to a hostname.
What is TTL and why does it matter?
Time To Live (TTL) is the number of seconds resolvers are allowed to cache a Domain Name System (DNS) record. A TTL of 300 means the record may be cached for up to 5 minutes. Lower TTLs allow faster propagation of changes; higher TTLs reduce DNS query load but mean old records stick around longer after a change.
Why do I get different results from different resolvers?
Results can differ due to caching (each resolver may have cached a different version), geo-DNS (some Content Delivery Networks (CDNs) return different IPs based on the resolver's location), or propagation delays after a recent Domain Name System (DNS) change. Use the DNS Propagation tool to query many resolvers simultaneously.