DNS lookup CLIs before a domain change
dig shows every reply's status and records, and can follow a delegation from the root. kdig shows the same detail with JSON and QUIC options. seer, our Rising Star, gives dig-style replies on Windows too. Doggo prints readable tables but hides the status of empty replies.
dig
Its default output names the response status and shows the answer and authority records, and it can ask a chosen server directly or trace a delegation.
Exit status 0 includes NXDOMAIN, so read the status. Use a current build: macOS has shipped an old one, and there is no Windows version.
Why dig is our PickTeam behind dig? Get your award badge
seer
A domain toolkit whose dig command prints the response status and flags, separates a missing name from an empty reply, traces delegations from the root and runs on Windows, macOS and Linux.
It asks Google Public DNS unless you name a server with @server, and it is new, fast-changing and has one human contributor.
Why seer earned Rising StarWho is this article for? Site owners comfortable with a terminal who need to read exact DNS answers and error replies before changing a domain.
About 29 min read
What Preferred Pick, Rising Star and Ready to Rock mean
The quick list
All four are free. Choose by your operating system and by how clearly you need to see failed and empty replies.
All four are free, open-source command-line tools with no account or subscription, checked October 19 to November 12, 2026. Licences: MPL 2.0 for dig (BIND), GPL 2.0 or later for kdig (Knot DNS 3.5.0 and later), MIT for seer and GPL 3.0 for Doggo. Your time to install and keep them updated is the main cost.
The comparison at a glance
Compare how each tool shows answers and failed replies, how you aim it at a server, and its 2026 maintenance and security record.
Order follows our verdict for reading DNS replies before a domain change, not popularity or speed. All tools remain selectable.
Hides matching answers for the selected tools. Unknowns and unverified claims stay visible.
| Feature | dig | kdig | seer | Doggo |
|---|---|---|---|---|
| Best fit | Reading full DNS replies on Linux or macOS, including following a delegation from the root | dig-style detail with JSON output or DNS over QUIC on Linux or macOS | dig-style replies and delegation tracing on Windows, macOS or Linux, from a broader domain toolkit | Quick tables of records that exist, on Windows, macOS or Linux |
| Cost and licence | $0; MPL 2.0; Internet Systems Consortium (ISC) | $0; GPL 2.0 or later since 3.5.0 (GPL 3.0 or later before); CZ.NIC | $0; MIT; Zac Roach, its only human contributor | $0; GPL 3.0; maintained mainly by its creator |
| Response status in the default view | Header names the status (NOERROR, NXDOMAIN or SERVFAIL), the flags and each section’s record count | Header names the status, the flags and each section’s record count; question, answer and authority shown by default | Prints the response status and header flags with the answer; tells a missing name (NXDOMAIN) from an empty reply (NODATA); other codes such as SERVFAIL appear as the status (README) | A Status column appears only when a returned SOA record carries a code other than NOERROR; a reply with no records shows no status, in the table or in JSON (1.4.1 source) |
| Exit status when a server replies | Documented: 0 for any reply, including NXDOMAIN; 9 when the server does not reply | Documented only as “0 means successful operation” | Documented: 0 for any answer, including NXDOMAIN, NODATA, SERVFAIL and REFUSED; 1 on a timeout or when no answer arrives | 0 for any reply; 9 when no server replies; 2 when only some do (1.4.1 source) |
| Asking a chosen or authoritative server | @server and -p port; +norecurse; +trace follows referrals from the root | @server, with a port if needed; +norecurse; no trace option | @server or -s; UDP with TCP retry; +trace from the root; no documented option to clear the recursion flag or to ask each authoritative server | @server; -A asks the domain’s authoritative nameservers (1.2.0); --trace (1.4.0) |
| Where you get it | Packaged by major Linux distributions; macOS ships an old build (9.10.6, reported in 2023); Homebrew 9.20.30; no Windows support since BIND 9.18 | Separate Linux package, often from a branch CZ.NIC no longer maintains; CZ.NIC’s own packages; Homebrew; no Windows version | Windows, macOS and Linux archives, a Homebrew tap, cargo, and PowerShell and shell installers; no distribution package found | Winget and Scoop on Windows; Homebrew and MacPorts on macOS; Linux packages and a single binary |
| Security record | 34 BIND advisories from January to September 16, 2026; they describe harm to the named server and resolver or to BIND as a whole, and none names dig. ISC announced more fixes for October 21 | One 2026 Knot DNS CVE, in a server signing module; kdig robustness fixes without a CVE in 3.5.5 and 3.6.1 | Release notes list dependency security fixes (rustls in 0.53.1, distrusted root certificates in 0.54.0); GitHub shows no security policy and no published advisories | No security policy and no published advisories |
| Reader reviews | No reviews yet. Write a review | No reviews yet. Write a review | No reviews yet. Write a review | No reviews yet. Write a review |
All four are free command-line tools. A zero exit status does not prove that a record exists; read the status and the answer. One reply from one server does not show what other resolvers have cached, or whether a website or mailbox works. Facts checked October 19 to November 12, 2026.
All features and sources 11 criteria
Open the groups that matter to you. They compare the same selected tools. “Planned” means future work, not an available feature. Sources include the published conditions.
Reading answers and failures
Show 3 criteria
| Feature | dig | kdig | seer | Doggo |
|---|---|---|---|---|
| Response status in the default view | Header names the status (NOERROR, NXDOMAIN or SERVFAIL), the flags and each section’s record count | Header names the status, the flags and each section’s record count; question, answer and authority shown by default | Prints the response status and header flags with the answer; tells a missing name (NXDOMAIN) from an empty reply (NODATA); other codes such as SERVFAIL appear as the status (README) | A Status column appears only when a returned SOA record carries a code other than NOERROR; a reply with no records shows no status, in the table or in JSON (1.4.1 source) |
| Missing name (NXDOMAIN) | Status in the header; the zone’s SOA under authority | Status in the header; the zone’s SOA under authority | “Name does not exist (NXDOMAIN)”, with the zone’s SOA when the server sends it | One SOA row named after the zone, not the name you asked for, with status NXDOMAIN |
| Exit status when a server replies | Documented: 0 for any reply, including NXDOMAIN; 9 when the server does not reply | Documented only as “0 means successful operation” | Documented: 0 for any answer, including NXDOMAIN, NODATA, SERVFAIL and REFUSED; 1 on a timeout or when no answer arrives | 0 for any reply; 9 when no server replies; 2 when only some do (1.4.1 source) |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for reading answers and failures
Read October 19, 2026: dig manual and return codes; kdig manual; seer README (DNS Queries and Exit Codes), read November 12, 2026; Doggo 1.4.1 table code, response model and exit codes; RFC 2308. Doggo rows are our reading of its source code; seer rows are the maker’s documentation, which we did not check against its code. A zero exit status never proves that a record exists.
Query control and formats
Show 2 criteria
| Feature | dig | kdig | seer | Doggo |
|---|---|---|---|---|
| Asking a chosen or authoritative server | @server and -p port; +norecurse; +trace follows referrals from the root | @server, with a port if needed; +norecurse; no trace option | @server or -s; UDP with TCP retry; +trace from the root; no documented option to clear the recursion flag or to ask each authoritative server | @server; -A asks the domain’s authoritative nameservers (1.2.0); --trace (1.4.0) |
| Transports and output formats | UDP, TCP, DNS over TLS and HTTPS; YAML output; companion tool delv validates DNSSEC | UDP, TCP, TLS, HTTPS and QUIC; JSON output; +validate is a debugging aid, not a security check | UDP, TCP, TLS and HTTPS; JSON and YAML output; separate DNSSEC and delegation commands | UDP, TCP, TLS, HTTPS (including HTTP/3), QUIC and DNSCrypt; JSON and short output |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Availability, maintenance and security
Show 5 criteria
| Feature | dig | kdig | seer | Doggo |
|---|---|---|---|---|
| Where you get it | Packaged by major Linux distributions; macOS ships an old build (9.10.6, reported in 2023); Homebrew 9.20.30; no Windows support since BIND 9.18 | Separate Linux package, often from a branch CZ.NIC no longer maintains; CZ.NIC’s own packages; Homebrew; no Windows version | Windows, macOS and Linux archives, a Homebrew tap, cargo, and PowerShell and shell installers; no distribution package found | Winget and Scoop on Windows; Homebrew and MacPorts on macOS; Linux packages and a single binary |
| Current release | BIND 9.20.30, October 2026; 9.20 supported to Q2 2028. 9.18 support ended June 2026 | Knot DNS 3.6.2, October 21, 2026; supported to Q3 2028 (3.5.10 to Q3 2027) | 0.58.0, November 2, 2026; 110 releases | 1.4.2, October 22, 2026; ten releases in 2026 after 13 months without one |
| Security record | 34 BIND advisories from January to September 16, 2026; they describe harm to the named server and resolver or to BIND as a whole, and none names dig. ISC announced more fixes for October 21 | One 2026 Knot DNS CVE, in a server signing module; kdig robustness fixes without a CVE in 3.5.5 and 3.6.1 | Release notes list dependency security fixes (rustls in 0.53.1, distrusted root certificates in 0.54.0); GitHub shows no security policy and no published advisories | No security policy and no published advisories |
| Cost and licence | $0; MPL 2.0; Internet Systems Consortium (ISC) | $0; GPL 2.0 or later since 3.5.0 (GPL 3.0 or later before); CZ.NIC | $0; MIT; Zac Roach, its only human contributor | $0; GPL 3.0; maintained mainly by its creator |
| Who maintains it | ISC | CZ.NIC | Zac Roach, its only human contributor | Its creator, with outside contributors |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for availability, maintenance and security
Read October 19, 2026: ISC downloads (read November 12, 2026), BIND vulnerability matrix, ISC announcement of May 11, 2026, ISC on Windows, macOS dig report; Knot DNS download (read November 12, 2026), 3.6.1 release notes, CVE-2026-39155; seer releases (read November 12, 2026); Doggo releases (read November 12, 2026) and security page; Debian, Ubuntu and Homebrew package records.
Earlier hands-on check, October 3, 2026
Show 1 criteria
| Feature | dig | kdig | seer | Doggo |
|---|---|---|---|---|
| Earlier hands-on check, October 3, 2026 (historical) | Ubuntu build of 9.18.39: exact A, MX, TXT and CAA records; NXDOMAIN, empty NOERROR and SERVFAIL told apart in the header; exit 0 for all three; 9 for no reply | Ubuntu kdig 3.3.4: the same records and statuses in a shorter layout; exit 0 for all three; 1 for no reply | Not part of the earlier check | Doggo 1.4.0: the same records; NXDOMAIN as one zone SOA row; empty NOERROR and SERVFAIL both only column headings, exit 0; 9 for no reply |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for earlier hands-on check, october 3, 2026
Historical observation from a small check on one Linux computer on October 3, 2026, before Practical Picks adopted its research-only method later that day. It queried a synthetic zone on a local test server, whose empty NOERROR reply carried no SOA record, unlike a server that follows RFC 2308. It did not decide any recommendation. Earlier check record, October 3, 2026; edge cases.
What matters when choosing
dig is our Preferred Pick for a site owner who wants to read exact DNS answers, and tell a missing name from an empty or failed reply, before changing a domain. Its default output opens with a header that names the response status (NOERROR, NXDOMAIN or SERVFAIL), the flags, including whether the reply is authoritative, and how many records each section holds. The question, answer and authority sections follow, with each record’s time to live (TTL). You can send the query to a server you name, ask an authoritative server directly with +norecurse, and follow the delegation from the root with +trace, which helps when the change involves nameservers. ISC, which maintains dig as part of BIND, documents what each exit code means. dig is free under the MPL 2.0, packaged by every major Linux distribution and preinstalled on macOS. dig manual
The compromises are real. dig’s default output is long, and the copy already on your computer may be old: in December 2023 a DNS operator reported that current macOS releases shipped dig 9.10.6, and we found no later report. BIND 9.18 and later do not support Windows, so on Windows you need the Windows Subsystem for Linux (WSL) or another tool. ISC ended support for BIND 9.18, which several Linux releases still ship, in June 2026, so fixes for those copies now depend on each distribution. ISC published 34 BIND vulnerabilities between January and September 16, 2026, against 8 in 2025, and said in May that language models had multiplied the reports it receives. Those advisories describe harm to named, the BIND server and resolver, or to BIND as a whole; none names dig. Some fixes are in BIND’s shared libraries, and ISC does not say whether dig is exposed, so keep it updated. ISC downloads, BIND vulnerability matrix, ISC on more frequent security updates, macOS report
seer is our Rising Star for readers who want dig-style replies on Windows as well as macOS and Linux. It is a broader domain toolkit, but its seer dig command prints the response status and header flags with the answer, says “Name does not exist (NXDOMAIN)” for a missing name and “No AAAA records (NODATA — the name exists)” for an empty reply, reports SERVFAIL and REFUSED as the status, and can follow a delegation from the root with +trace. It offers Windows, macOS and Linux downloads, a Homebrew tap and cargo. It is new: its first published version is from January 2026, it has published 110 releases, and it has one human contributor. Unless you name a server with @server, it asks Google Public DNS. It scored highest of the newer tools we found, 3.80 against 3.03 for the next, zns, but our scores rest on its README and release notes, not on code we read. seer project, releases
Disclosure: Practical Picks articles are researched and written with AI, currently Anthropic’s Claude. seer, our Rising Star, offers an MCP server and documents its use with Claude Desktop. We have no relationship with the project or with Anthropic over this article, and this integration carried no weight in our judgment.
Choose Doggo when you want a readable table of records that exist. It runs on Windows, macOS and Linux, but when a reply carries no records, as most server failures do, it shows no status at all, so an empty table can hide a SERVFAIL. For NXDOMAIN, the one row it prints is the zone’s SOA record, named after the zone rather than the name you asked for. Doggo project, table code, response model
Do not treat a zero exit status as proof that a record exists or that a change worked. dig exits 0 whenever a server replies, NXDOMAIN included. kdig’s manual says only that 0 means “successful operation”, seer’s documentation says its dig command exits 0 for any answer, and Doggo’s code exits 0 whenever any reply arrives. Read the status and the answer itself. One reply from one server also says nothing about what other resolvers have cached, or whether a website or mailbox works.
Choose kdig when you want the same packet detail with JSON output or DNS over QUIC on Linux or macOS. CZ.NIC’s kdig shows the header, status, question, answer and authority sections by default, as dig does, and adds JSON output and QUIC transport. It cannot trace a delegation from the root, it is rarely preinstalled, distributions often package an older branch, and there is no Windows version. CZ.NIC released 3.6.2 on October 21, 2026; its one 2026 vulnerability was in the Knot DNS server’s online-signing module, not in kdig. kdig manual, Knot DNS download
dig
Preferred Pick · reading DNS replies before a change
Choose dig to read exact records and the response status from a server you name, and to follow a delegation from the root. Use a current build: the copy macOS ships has been old, and there is no Windows version.
Reasons to choose it
- Header shows the status, flags and record counts for every reply
- +norecurse and +trace for checking authoritative servers and delegations
- Exit codes documented; packaged for every major Linux distribution
What to watch
- Long default output; +short hides the status
- macOS has shipped dig 9.10.6; no Windows support since BIND 9.18
- Many 2026 BIND fixes; none names dig, but keep it updated
dig prints the whole reply by default. Its manual describes the comment lines that carry “information about the packet header and OPT pseudosection, and the names of the response section”, and these are on unless you turn them off. The header line names the status and the flags line shows whether the server answered authoritatively and how many records sit in the answer and authority sections, so an NXDOMAIN with the zone’s SOA, an empty NOERROR and a SERVFAIL look different. +short prints only record values and hides that status, so avoid it for this job. Name the server with @server and a port with -p; +norecurse asks an authoritative server without requesting recursion, and +trace follows referrals from the root servers to the name. Current versions also support TCP, DNS over TLS and DNS over HTTPS. +yaml gives structured output, and BIND’s companion tool delv validates DNSSEC answers with the same logic as the BIND resolver. DNS providers’ help pages often use dig in their examples, as Cloudflare’s DNS debug endpoints page does. dig manual, delv manual, Cloudflare debug endpoints
ISC documents dig’s exit codes: 0 when a DNS response was received, “including NXDOMAIN status”, 1 for a usage error, 8 when a batch file cannot be opened, 9 when the server does not reply and 10 for an internal error. A SERVFAIL reply is also a received response. Read the header before you act on any result. Return codes
Read the full dig analysis and sources
Which dig you have depends on your system. ISC’s current release is BIND 9.20.30, from October 2026, and the 9.20 branch is supported until the second quarter of 2028. ISC ended 9.18 with 9.18.50 in June 2026 and has deferred the next stable branch, 9.22, to at least the end of 2026. As of October 19, Debian 13 shipped 9.20.29, Debian 12 shipped 9.18.49, and Debian’s tracker still listed September’s server flaws as unfixed there. Ubuntu 24.04 kept version 9.18.39 and added its own fixes to it, for example for CVE-2026-10822 and CVE-2026-75029. Homebrew offers 9.20.30 on macOS, which is the way to replace the old system copy. On Windows, ISC announced in June 2021 that BIND 9.18 “will not come with Windows as supported platform”. ISC downloads, BIND 9.20 release notes, Debian bind9 tracker, Ubuntu CVE-2026-10822, Homebrew bind, ISC on Windows
BIND’s security record in 2026 is busy but concerns its server. ISC’s matrix lists 34 vulnerabilities published from January 21 to September 16, 2026, against 8 in 2025. On May 11, ISC told users to expect security fixes in every monthly release: language models had made flaws easier to find, and it was triaging reports, “both from external reporters and our own LLM analysis”, at more than ten times historic levels. The advisories describe attacks on named, mostly its resolver, and none names dig. One, CVE-2026-10822, concerns invalid DNSKEY data that “may lead to unexpected exit” and names only “BIND 9” as the program affected, without saying whether dig is. One 2026 fix did concern a client tool: BIND 9.20.20 fixed a memory flaw that “only affected the delv tool”. ISC announced further security fixes for October 21, 2026, the month it published 9.20.30; whether any of them reaches dig is unconfirmed. BIND vulnerability matrix, CVE-2026-10822, ISC announcement, May 11, 2026, October pre-announcement
In an earlier hands-on check on October 3, 2026, before we adopted our research-only method, Ubuntu 24.04’s dig build 9.18.39-0ubuntu0.24.04.7 queried a small synthetic zone on the same computer. It printed the exact A, MX, TXT and CAA records with their TTLs, and its header told NXDOMAIN, an empty NOERROR and SERVFAIL apart. It exited 0 for all three and 9 when the server stayed silent. Because that test server offered no recursion, dig printed a “recursion requested but not available” warning, which is expected when you ask an authoritative server. The check covered one zone on one Linux computer and decided nothing here. Earlier check record, October 3, 2026, edge cases
Used dig? Share your experience to help other readers choose.
kdig
Alternative · JSON output or DNS over QUIC
Choose kdig when you want dig-style detail with JSON output or DNS over QUIC on Linux or macOS, and can install a current package.
Reasons to choose it
- Shows the status, flags and record counts by default
- JSON output and TLS, HTTPS and QUIC transports
- Supported branches with published end dates
What to watch
- No option to trace a delegation from the root
- Distributions often ship an older, unmaintained branch
- No Windows version; exit status only loosely documented
kdig comes from Knot DNS, an authoritative DNS server developed by CZ.NIC. Its manual marks the options that are on by default: the header, comment lines, question, answer, authority and additional sections, the TTL and class, and closing statistics. Like dig, it therefore shows the status and section counts for every reply. You name the server with @server and can add a port to the address. +norecurse clears the recursion flag, +tcp, +tls, +https and +quic choose the transport, and +json prints the reply in the RFC 8427 JSON format. Knot DNS 3.6.0 added +validate, which the manual says “is not a security feature, rather a debugging tool”, because kdig does not check the whole chain of trust. kdig has no option to trace a delegation from the root. Its manual says only that “Exit status of 0 means successful operation. Any other exit status indicates an error”, without saying how NXDOMAIN or SERVFAIL count. kdig manual
CZ.NIC keeps two branches. Knot DNS 3.6.2, released October 21, 2026, is supported until the third quarter of 2028, and 3.5.10, released the same day, until the third quarter of 2027. Since 3.5.0, in September 2025, the project has been licensed under the GPL 2.0 or later; earlier releases used the GPL 3.0 or later. CZ.NIC publishes security fixes in its release notes rather than in a separate advisory list. Its one 2026 vulnerability, CVE-2026-39155, was in the server’s online-signing module and was fixed in 3.4.10 and 3.5.4 in April. Recent release notes also list kdig fixes without a CVE: undefined behaviour when +https and +quic were combined (3.5.5, June 2026) and a missing check for malformed EDNS data in replies (3.6.1). Knot DNS download, 3.6.1 release notes, 3.5.4 release notes, Debian CVE-2026-39155, licence change, 3.5.0
Read the full kdig analysis and sources
Getting a current kdig takes a step. Distributions package it separately (knot-dnsutils on Debian and Ubuntu) and often ship a branch CZ.NIC no longer maintains: 3.2.6 in Debian 12, 3.4.6 in Debian 13 and 3.3.4 in Ubuntu 24.04, where it sits in the community-maintained universe section. CZ.NIC publishes its own Debian and RPM packages, and Homebrew carries 3.6.2. Knot DNS runs on “most UNIX-like systems, such as Linux, *BSD, and macOS”; there is no Windows version. Requirements, Debian knot packages, Ubuntu package, Homebrew knot
In an earlier hands-on check on October 3, 2026, before we adopted our research-only method, Ubuntu’s kdig 3.3.4 queried the same synthetic zone. It printed the same four records, and its header named NXDOMAIN, an empty NOERROR and SERVFAIL. It exited 0 for all three, and 1 with an error on standard error when the server stayed silent. Its layout was shorter than dig’s, but it carried the same information, so layout did not decide this comparison. Earlier check record, October 3, 2026, edge cases
Used kdig? Share your experience to help other readers choose.
seer
Rising Star · a newcomer worth considering
Why Rising Star? Seer scored highest of the eligible newer DNS lookup tools we found. Its README says it prints the response status and flags, tells a missing name from an empty reply, follows delegations from the root and offers Windows, macOS and Linux downloads. Our scores rest on that documentation, not on code we read. This is not our broader Ready to Rock endorsement.
Consider seer if you want dig-style replies, with the response status and flags, on Windows as well as macOS and Linux. Name the server with @server, because it otherwise asks Google Public DNS.
Reasons to choose it
- Prints the response status and flags, and tells a missing name from an empty reply
- @server, +trace from the root, DNS over TLS and HTTPS, JSON output
- Windows, macOS and Linux downloads; exit codes documented
What to watch
- Asks Google Public DNS unless you name a server
- New and fast-changing: 110 releases, one human contributor
- Our scores rest on its documentation, not on code we read
seer is a domain toolkit written in Rust by Zac Roach and published under the MIT licence. Besides WHOIS, RDAP, SSL and HTTP checks, it has a dig command that takes its arguments in any order, for example seer dig @8.8.8.8 example.com MX. Its README says seer dig “reports a query the way dig does: the response status, the header flags, and the answer”, shows which server answered and how long it took, and shows the response “exactly as the server sent it”. It tells a missing name from an empty reply, shows the zone’s SOA “when the server sends it”, and reports SERVFAIL, REFUSED and other codes as the status rather than as errors. +trace asks one server of each zone from the root down and prints one hop per delegation level. It speaks UDP with a TCP retry, DNS over TLS and HTTPS, prints JSON or YAML, and has separate commands for DNSSEC, delegation checks and comparing two servers. CAA is among its record types. The README documents its exit codes: seer dig is “not a check command”, and any answer the server gave exits 0, “NXDOMAIN, NODATA, SERVFAIL and REFUSED included”. README
Its limits for this job: the README describes no option to clear the recursion flag or to ask each of a zone’s authoritative servers directly, which dig does with +norecurse and Doggo with -A. When you name no server it asks Google Public DNS, so name one with @server when the names are not meant to be shared. +short prints nothing when there is no answer, so it hides the status as dig’s does. We read its documentation and release notes but not its code, and ran nothing.
Read the full seer analysis and sources
seer offers Windows, macOS and Linux archives with every release, a Homebrew tap (brew install TheZacillac/tap/seer), cargo install seer-cli, and shell and PowerShell installers. These are the maker’s own channels; we did not look for distribution packages. Releases
seer is new and changes fast. It has published 110 releases, the latest 0.58.0 on November 2, 2026, and had commits on the day we read it. Its crate listing shows 108 published versions, the first (0.1.3) on January 16, 2026. Its release notes list security fixes for dependencies, for example four rustls advisories in 0.53.1 and the removal of distrusted root certificates in 0.54. Zac Roach is its only human contributor; the other two listed are automated accounts. GitHub shows no security policy and no published advisories for it, and the OSV vulnerability database lists none for seer-cli. Release notes, crate listing, GitHub security page, OSV
Used seer? Share your experience to help other readers choose.
Doggo
Alternative · quick tables of records that exist
Consider Doggo for quick tables of records that exist, on Windows, macOS or Linux. When its table is empty, check the reply with another tool before you act.
Reasons to choose it
- Installs with Winget, Scoop, Homebrew or as one binary
- Readable table with TTL and the nameserver that answered
- Trace and authoritative-server options added in 2026
What to watch
- A reply with no records shows no status, even in JSON
- NXDOMAIN appears as a zone SOA row, not the name you asked for
- One main maintainer; no security policy
Doggo’s first release, 0.1.0, came on December 18, 2020. Doggo calls itself a “Command-line DNS client for humans”. It prints answers as a table of name, type, class, TTL, value and the nameserver that answered, and offers JSON and short output. It speaks UDP, TCP, DNS over TLS, HTTPS and QUIC, and DNSCrypt. In 2026 it added an --authoritative/-A option that asks the domain’s authoritative nameservers (1.2.0, June), reporting of extended DNS errors (1.3.0, August) and iterative --trace (1.4.0, September). It installs with Winget and Scoop on Windows, Homebrew and MacPorts on macOS, and as Linux packages or a single binary. It is free under the GPL 3.0. Two optional features send your queries through outside services: the Globalping option, which asks probes on a third-party network, and the hosted web interface. Use them only for names you are content to share with those services. README, 1.2.0, 1.3.0, 1.4.0
Its weakness for this job is how it reports replies without records. In the 1.4.1 source, the table gains a Status column only when a returned SOA record carries a code other than NOERROR, and the response itself has no status field, in the table or in JSON. A SERVFAIL usually carries no records, so Doggo prints only the column headings. An empty NOERROR from a properly configured authoritative server includes the zone’s SOA, which RFC 2308 requires, so Doggo shows that SOA row, without a status. For NXDOMAIN it shows the SOA row named after the zone, with the status beside it. The code also skips authority records other than SOA, so a referral from a parent zone’s server shows any glue addresses but not the delegated NS records; use --trace or -A for delegation checks. The maintainer added that Status column in December 2020, after a user asked for error codes to be printed. Doggo exits 0 when any reply arrives, 9 when no server answers and 2 when only some do. Table code, response model, exit codes, issue 5, RFC 2308
Read the full Doggo analysis and sources
Doggo is maintained mainly by its creator, with outside contributions. It shipped ten releases in 2026, the latest 1.4.2 on October 22, after 13 months without a release between September 2024 and October 2025. Fixes can be quick: a May 2026 report that --strategy=first ignored nameservers given on the command line was fixed in 1.1.7 five days later. The project publishes no security policy and has no published advisories. Version 1.2.0 renamed its download files, so scripts that fetched the old names needed updating. Releases, issue 238, security page
In an earlier hands-on check on October 3, 2026, before we adopted our research-only method, the upstream Doggo 1.4.0 binary queried the same synthetic zone. It showed the four records exactly. For NXDOMAIN it printed one SOA row for the zone with the status NXDOMAIN. An empty NOERROR and a SERVFAIL both produced only column headings and exit 0; that test server sent no SOA with its empty reply, unlike a server that follows RFC 2308. It exited 9 when the server stayed silent. These results match the source code described above. Earlier check record, October 3, 2026, edge cases
Used Doggo? Share your experience to help other readers choose.
Which product are we missing?
Know a product that belongs in this article? Tell us what it does differently and why it deserves a closer look. Newcomers welcome.
Readers and product teams can suggest candidates. Suggestions inform our research; they do not guarantee inclusion or a recommendation.
Opens an email draft with this article attached as a link. Nothing is sent until you send it.
No email app? Send the product name, website, and this article’s title to admin@practicalpicks.guide.
What people are saying
We have no Practical Picks reader reviews for these tools yet.
The most practical user reports concern versions and failure display. On the DNS-OARC operators’ list in December 2023, a user found that macOS Ventura and Sonoma shipped dig 9.10.6 after a lookup of a newer record type failed; another reply suggested Homebrew’s BIND for a current version. Doggo’s tracker shows a user asking in 2020 that “Unless it is NoError, error code should be printed”, which led to its Status column, and a 2023 report of NXDOMAIN rows naming an unexpected domain, for which the maintainer pointed to the computer’s search-domain settings. macOS report, Doggo issue 5, Doggo issue 63
We found no independent reports or reviews of seer. Homebrew’s install counts for the 12 months to October 19, 2026 give a rough sense of use among macOS and Linux developers who use it: about 17,400 installs of BIND, which includes dig and the server, 10,500 of Doggo and 3,000 of Knot DNS, which includes kdig and the server. Most Linux and macOS users get dig without Homebrew, so these are not market shares. BIND, Doggo, Knot DNS
How we researched
This is public-source research. For this review we did not install, run or test any of these tools, create accounts or contact the projects. Our sources were each project’s manuals, release notes, security advisories and announcements (ISC’s vulnerability matrix and advisories, CZ.NIC’s release notes, GitHub, the OSV database), source code, issue trackers, package records (Debian, Ubuntu, Homebrew and Go’s module mirror), standards documents and user discussions, read on October 19, 2026, with release pages, the newer-tool search and seer read on November 12, 2026. No project supplied access or payment, and our links carry no affiliate tracking.
This comparison first rested on a small hands-on check run on October 3, 2026, before we adopted our research-only method later that day. It sent the same queries for four synthetic records, a missing name, an empty reply, a server failure and no reply to a test server on one Linux computer, and captured each command’s output and exit status. We keep it only as a dated observation. It shows how three specific builds displayed those replies once, not how the tools behave with real resolvers, DNSSEC or other systems, and it did not decide any recommendation here. An earlier draft based mainly on that check preferred kdig for its shorter display; on public evidence kdig and dig show the same information, and dig’s availability, delegation tracing and documented exit codes decide it. Earlier check record, October 3, 2026, edge cases, test server and commands
We wrote this for someone comfortable in a terminal who is about to change a domain’s DNS and wants to read exact records from a server they choose, telling a missing name, an empty reply, a server failure and no reply apart. Before scoring, we fixed five criteria and their weights: reading answers and response status (30%), query control for a domain change, such as choosing the server, asking it without recursion and following the delegation (20%), maintenance, security and continuity (25%), availability on Windows, macOS and Linux (15%), and documentation (10%). All four are free, so cost carried no weight. dig led kdig by 0.45 on our five-point scale, seer by 0.58 and Doggo by 1.00, and stayed ahead when we removed availability, gave query control more weight, or scored the tools for a Windows user with WSL. seer and Doggo run on Windows without WSL; dig and kdig do not.
We checked that every widely used option for this reader was either compared or set aside for a stated reason. host and nslookup come from the same BIND distribution as dig, with simpler output and fewer controls. drill, from NLnet Labs’ ldns, had a 2026 flaw (CVE-2026-10846) that let an attacker off the network path forge its replies; it was fixed in ldns 1.9.1 in June, but Debian 12 and 13 still listed their packages as vulnerable on October 19. dog has had no release since November 2020 and no change since October 2021. AdGuard’s dnslookup takes the record type and most options from environment variables rather than arguments. resolvectl query asks the systemd-resolved service on a Linux computer and cannot be pointed at a server you name. PowerShell’s Resolve-DnsName on Windows does not list CAA among its record types. On November 12, 2026, we searched again for newer tools on Hacker News, GitHub topic lists, Rust crate listings and the tool lists we used before, and re-tested the ones we had set aside. A tool counts as newer when its own first public release is within the last two years. Two cleared that test and our other conditions (available now, shown by their own documentation or code to read DNS replies from a server you name, still maintained, no known unpatched serious flaw in the current release): seer (first published version: January 2026) and zns (first release February 2025). seer scored 3.80 and zns 3.03, so seer is our Rising Star. Its lead is wide on our numbers, but it rests on seer’s documentation rather than code we read; it would still lead if we scored its reply display, query control and maintenance each a full point lower. zns says in words when a name does not exist or a query fails, but shows no flags or authority records, and its DNSSEC checks, Windows support, tracing and exit codes all arrived in one day in July 2026. Doggo (December 2020, 3.38), q (2021, 3.30), ch4 (2021, 3.08), awl (2022) and doge (2.93; a 2024 continuation of dog, which was first released in 2020) are older than two years, so none can be the Rising Star. q prints nothing for a missing name unless you ask for statistics, all sections or its dig-style format; a request to change that, opened in February 2026, has since been closed. ch4 shows dig’s header but shows CAA records only as raw hexadecimal and installs only through Rust’s cargo. doge prints a status line for errors but cannot turn off recursion or trace a delegation. awl, first published in 2022, would have scored 3.50: it shows dig’s full reply by default and has Windows builds. We did not include it, because its only current release, 0.6.14 from October 15, 2024, includes a networking library with a flaw rated high, CVE-2025-59530, that lets a malicious DNS-over-QUIC server crash it, and the fix is merged but unreleased. dug, released in June 2025, scored 2.98 but has had no release since then and no change except dependency updates, so we treat it as abandoned. dotdig prints “(no records)” and no status for a missing name or a failure, digr has no release, and zoneglint compares public resolvers rather than asking a server you name. dqy and dnsl have had no release or code change for more than a year, and the other new tools we found lacked CAA records, could not query a server you name, or were web services, resolvers or developer utilities.
| Tool | Public sources | What remains uncertain |
|---|---|---|
| dig | BIND manual pages and release notes, ISC download page, vulnerability matrix and advisories, ISC announcements of May and October 2026, ISC’s 2021 Windows notice, Debian and Ubuntu security trackers, Homebrew record, DNS-OARC report. | Whether any 2026 BIND flaw reaches dig, the contents of ISC’s October 21 release, the dig version current macOS ships. |
| kdig | kdig manual, requirements and download pages (read again November 12), release notes to 3.6.1, Debian, Ubuntu and Homebrew records, CVE-2026-39155 records. | How older distribution builds handle malformed replies, whether CZ.NIC will publish a separate advisory list. |
| seer | README, release notes and release page to 0.58.0, crate listing, repository and security pages, OSV. | Whether its output matches the README (we read no code and ran nothing), whether the project keeps its pace with one human contributor, how its default use of Google Public DNS suits your names. |
| Doggo | README, releases 1.1.4 to 1.4.2, source code at 1.4.1, issue tracker, security page, Homebrew record. | Whether a future release shows the response status for replies without records, continuity with one main maintainer. |
None of these sources measures speed, accuracy against real resolvers or behaviour under attack. Next substantive review is due December 18, 2026, or sooner if a BIND, Knot DNS, seer or Doggo release changes how replies are shown or patched. Found a change? Contact the editors.
Sources and evidence
Checked October 19, 2026, except where marked November 12 (ISC downloads and Homebrew for BIND, Knot DNS downloads, Doggo and seer releases, the newer-tool search): BIND and dig manual pages, release notes, ISC downloads, vulnerability matrix, advisories CVE-2026-10822, CVE-2026-75029 and CVE-2025-13878, ISC announcement, May 11, 2026, October 2026 pre-announcement, ISC on Windows, June 2021, Debian bind9 tracker, Ubuntu CVE-2026-10822, Homebrew bind, DNS-OARC macOS report and Cloudflare debug endpoints; Knot DNS and kdig manual, requirements, download and support periods, 3.6.1 release notes, 3.5.4 release notes, NEWS, Debian CVE-2026-39155, Debian knot packages, Ubuntu knot-dnsutils and Homebrew knot; seer project and releases, read November 12, 2026 with the crate listing, GitHub security page and OSV search; Doggo project, releases, table code, response model, exit codes, issues 5, 63 and 238, security page and Homebrew doggo; newer tools, checked October 20 and November 12, 2026: Doggo first release, q, ch4, doge, dqy, dnsl, and awl’s releases, 0.6.14 dependencies and CVE-2025-59530; set-aside tools: ldns changelog, Debian CVE-2026-10846, q issue 158, dog, dnslookup, resolvectl, Resolve-DnsName zns with its releases, dug, dotdig and digr; RFC 2308; and the earlier check record, October 3, 2026, with its edge cases, test server and commands. No project supplied access or influenced the conclusion. No affiliate links were used. Recheck ISC’s October 21 advisories, seer’s advisory page, the Doggo release notes and the distribution package versions before any public release.
No screenshots are shown: these are command-line tools, and this review is based on public sources. The earlier check record, October 3, 2026 keeps the commands and output from a small check on a synthetic zone before our research-only method.