DNS lookup
Check DNS records across public resolvers with a dig-style answer view.
A practical guide to DNS lookup
DNS Lookup sends a DNS-over-HTTPS wire-format query for a chosen record type and shows answers, TTLs, response flags, and DNSSEC-related data. It is a diagnostic client, not a zone editor.
Example: verify a new mail configuration
Query MX for the domain, inspect the returned priorities and TTLs, then check TXT records for SPF and compare results after the expected propagation window.
Task-specific steps
- 1
Enter a domain name without a URL path and choose the record type you need to inspect.
- 2
Run the query and review the answer, authority, response code, TTL, and validation information.
- 3
Compare the result with the intended DNS change and account for caching before declaring propagation complete.
Options that affect the result
- Record types cover common address, mail, alias, text, authority, and DNSSEC investigations.
- The raw response view exposes protocol details when the summarized answer is not enough.
Limitations to know first
- The query contacts an external DNS-over-HTTPS resolver and therefore requires network access.
- One resolver's cached answer may differ temporarily from authoritative servers or resolvers in other regions.
Questions specific to this task
Why does DNS Lookup show an old value after I changed it?
Recursive resolvers can serve cached data until its TTL expires. Authoritative updates and caches also propagate on different timelines.
Does a DNSSEC record mean the answer is validated?
Not by itself. Validation depends on a complete chain of trust, valid signatures, supported algorithms, and how the selected resolver reports authenticated data.