Zdns
ZDNS is a high-speed DNS resolver and command-line tool for performing large-scale DNS measurements.
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
57/100 Fair
- Maintained
- 100last commit 33 days ago
- Popular
- 611,156 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- No data
- Security check
- 07 serious findings, 7 minor, CI, tests, OpenSSF Scorecard 5.3/10
Based on 4 of 5 factors.
Security check: 7 serious findings
- Uses golang.org/x/crypto v0.49.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.49.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.49.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.49.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.49.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.49.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.49.0, which has a known critical vulnerability (Go)
Automated checks on commit df6af70, 26 Oct 2026. Not an audit.
- GitHub stars
- 1,156
- Open issues
- 5
- Last commit
- 2026-10-18
- Latest release
- v2.1.1
- License
- Apache-2.0
- Activity
- stale
Checked 2 days ago - source: GitHub (zmap/zdns)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Have Git and Go before building Before cloning ZDNS and running make install, make sure Git and Go (Golang) are already installed on your machine. Without them, the build commands will fail and you won’t get the zdns command to use. source
- Confirm zdns works after install Run zdns --version after the install finishes. If it says command not found, the install didn’t complete or your system can’t find the installed binary, so queries won’t work. source
- Use a working DNS name server By default, zdns asks your system’s DNS servers (the service that turns domain names into IP addresses) from /etc/resolv.conf. If queries fail, point it at a known DNS server with --name-servers, for example: zdns A google.com --name-servers=1.1.1.1. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
How do I install ZDNS from source?
Clone the ZDNS repository and run make install inside the checkout.
What should I do if ZDNS queries fail with the default DNS configuration?
The default resolver reads system DNS servers from /etc/resolv.conf. If lookups fail, specify a working name server with --name-servers.
How should I use multiple Resolver structs when doing parallel DNS lookups?
A single Resolver should perform only one lookup at a time because it is not thread-safe. Create multiple Resolver structs to run lookups in parallel.
What do raw DNS modules return?
Raw DNS modules return the raw DNS response from the server in JSON form, similar to dig. They cover nearly every DNS record type.
Answers sourced from github.com, github.com
Community
Collected 48 days ago - public community threads