Check a DNS zone file before upload: named-checkzone, named-compilezone, kzonecheck and validns
Choose named-checkzone before uploading a hand-edited file. It leads narrowly over named-compilezone because it needs fewer settings; read every warning, or use kzonecheck when a script must stop on any finding.
named-checkzone
Choose it for syntax, CNAME conflicts, MX, SRV and NS targets and required glue. It leads narrowly, 4.10 to named-compilezone’s 4.00, because it needs fewer settings.
Missing addresses and missing glue are only warnings: it still prints OK and exits 0. Read every line, and run it with -i local to avoid network lookups.
Why named-checkzone is our PickTeam behind named-checkzone? Get your award badge
No Rising Star selected
bindlint offers line-numbered explanations and configurable failure thresholds, but we have not established support for both Windows and macOS.
Its documentation also says included files are not followed, DNSSEC is not validated and glue consistency checks remain planned.
Who is this article for? People who edit a BIND-style DNS zone file by hand and want to catch mistakes on their own computer before uploading it to a DNS host.
About 24 min read
What Preferred Pick, Rising Star and Ready to Rock mean
The quick list
Start with named-checkzone and read every warning before upload. Choose named-compilezone for conversion too, kzonecheck for strict failure handling or signed zones, and validns for line-numbered DNSSEC and policy checks.
All four are free, open-source tools with no account or subscription, checked November 8, 2026. None has a native Windows build; on Windows use the Windows Subsystem for Linux. Installing them and keeping them updated still takes time.
The comparison at a glance
Compare which mistakes each checker documents that it catches, whether a finding changes the exit status, and how current and safe the packaged versions are.
named-checkzone comes first for a hand-edited file before upload, narrowly ahead of named-compilezone. kzonecheck and validns follow; choose kzonecheck for strict failure handling or a signed zone.
Hides matching answers for the selected tools. Unknowns and unverified claims stay visible.
| Feature | named-checkzone | named-compilezone | kzonecheck | validns |
|---|---|---|---|---|
| Best fit | Choose named-checkzone for a hand-edited file; read every warning before upload | Choose named-compilezone when conversion is also needed and you can configure its checks | A script that must stop on any finding, or a zone that is already DNSSEC-signed | Strict, line-numbered reports and DNSSEC chain checks, if you can install 0.11 |
| Cost and licence | $0; MPL-2.0 (part of BIND) | $0; MPL-2.0 (part of BIND) | $0; GPL-2.0 or later since 3.5.0 (part of Knot DNS) | $0; BSD-2-Clause |
| MX, SRV and NS targets have addresses | Checked: -i local for names in your zone; default full mode also checks names outside it. Warning only | Available with -i local for in-zone targets; integrity mode defaults to none. Warning only | Not checked | Not checked (mx-alias and ns-alias only flag targets that are CNAMEs) |
| Missing glue for a delegated child | Checked; warning only. Could be skipped before 9.20.23 and 9.18.49 (May 2026) | Available with -i local; disabled by default. Read every warning | Checked; non-zero exit. A false warning was fixed in 3.4.7 (June 2025) | Only with -p missing-glue, added in 0.11.0 (July 2026) |
| Exit status when it finds a problem | 1 for load errors; 0 with OK for missing addresses and glue, and no option changes that. -q prints nothing | 1 for errors, 0 otherwise; integrity warnings still need reading; -q hides output | Non-zero for every finding | Non-zero for every reported error; -f stops at the first |
| Current release, checked November 8, 2026 | BIND 9.20.30, October 21, 2026; 9.20 supported until Q2 2028; 9.18 end of life since June 2026 | BIND 9.20.30, October 21, 2026; 9.20 supported until Q2 2028 | 3.6.2, October 21, 2026, supported until Q3 2028; 3.5.10 until Q3 2027 | 0.11.0, July 15, 2026; no release between February 2014 and January 2026; two maintainers |
| 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 compared tools are free command-line tools that read a zone file on your computer. None can tell you whether your DNS host will accept the file, whether the parent zone delegates correctly or whether mail will be delivered. Prices and current releases checked November 8, 2026; unchanged checks and packaging evidence from October 19, 2026. named-checkzone leads narrowly, 4.10 to named-compilezone’s 4.00, because it needs fewer settings for this job.
All features and sources 12 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.
What each checker catches
Show 4 criteria
| Feature | named-checkzone | named-compilezone | kzonecheck | validns |
|---|---|---|---|---|
| Syntax errors and CNAME conflicts | Stop the load; exit status 1, naming the file line | BIND syntax and CNAME load checks; stricter checking needs explicit settings | Mandatory checks; non-zero exit status | Syntax always checked, with file and line; CNAME conflicts only with -p cname-other-data |
| MX, SRV and NS targets have addresses | Checked: -i local for names in your zone; default full mode also checks names outside it. Warning only | Available with -i local for in-zone targets; integrity mode defaults to none. Warning only | Not checked | Not checked (mx-alias and ns-alias only flag targets that are CNAMEs) |
| Missing glue for a delegated child | Checked; warning only. Could be skipped before 9.20.23 and 9.18.49 (May 2026) | Available with -i local; disabled by default. Read every warning | Checked; non-zero exit. A false warning was fixed in 3.4.7 (June 2025) | Only with -p missing-glue, added in 0.11.0 (July 2026) |
| DNSSEC signatures | Not checked by named-checkzone; BIND’s separate dnssec-verify does this | Not checked; use BIND’s separate dnssec-verify | Validated automatically when the SOA record is signed; ZONEMD with -z | Signatures and NSEC/NSEC3 chains always checked in a signed zone |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for what each checker catches
BIND manuals read November 8, 2026; other unchanged documentation and source code read October 19, 2026: named-checkzone manual, Knot semantic checks, validns README, named-compilezone manual; glue fixes in ISC merge request 11899 and Knot’s release history. Documented behaviour, not measured accuracy.
Results and network use
Show 2 criteria
| Feature | named-checkzone | named-compilezone | kzonecheck | validns |
|---|---|---|---|---|
| Exit status when it finds a problem | 1 for load errors; 0 with OK for missing addresses and glue, and no option changes that. -q prints nothing | 1 for errors, 0 otherwise; integrity warnings still need reading; -q hides output | Non-zero for every finding | Non-zero for every reported error; -f stops at the first |
| Looks up names over the network | Yes in the default full mode, through your resolver; not with -i local | No integrity lookups by default; -i local enables local checks; full mode can resolve external names | No lookups documented | No lookups documented |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for results and network use
BIND manuals read November 8, 2026; unchanged evidence read October 19, 2026: the 2009 operators’ thread on named-checkzone’s exit status, and source code for named-checkzone, kzonecheck and validns.
Setup, maintenance and security
Show 5 criteria
| Feature | named-checkzone | named-compilezone | kzonecheck | validns |
|---|---|---|---|---|
| Cost and licence | $0; MPL-2.0 (part of BIND) | $0; MPL-2.0 (part of BIND) | $0; GPL-2.0 or later since 3.5.0 (part of Knot DNS) | $0; BSD-2-Clause |
| Install | bind9-utils on Debian and Ubuntu, without the server; Homebrew bind, about 17,400 installs in 12 months. No Windows build since BIND 9.16 | Same BIND packages as named-checkzone; requires -o output and explicit integrity and warning settings; no native Windows build | knot-dnssecutils on Debian and Ubuntu; CZ.NIC’s own packages; Homebrew knot, about 3,000 installs in 12 months. No Windows | Distribution packages mostly old; DNS-OARC packages for Debian and openSUSE; no Homebrew. Building needs the Judy library |
| Current release, checked November 8, 2026 | BIND 9.20.30, October 21, 2026; 9.20 supported until Q2 2028; 9.18 end of life since June 2026 | BIND 9.20.30, October 21, 2026; 9.20 supported until Q2 2028 | 3.6.2, October 21, 2026, supported until Q3 2028; 3.5.10 until Q3 2027 | 0.11.0, July 15, 2026; no release between February 2014 and January 2026; two maintainers |
| Version in Ubuntu 24.04 | 9.18.39 with Ubuntu security updates; predates ISC’s May 2026 glue-check fix | Same BIND 9.18.39 package; whether the May 2026 glue fix was backported is unconfirmed | 3.3.4; predates the 2025 false-glue fix | 2017 snapshot; predates the missing-glue policy and the July 2026 parser fixes |
| Security record, 2026 | 38 flaws fixed January to October 2026, including four in 9.20.30 on October 21; descriptions concern the named server, none names named-checkzone | Shares BIND’s security record; October 21 fixes concern server DNS messages, not local file checking | CVE-2026-39155 concerns the server’s online-signing module, not kzonecheck | 0.11.0 fixed buffer overflows in its zone-file parser (no CVE); older packages lack the fix |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for setup, maintenance and security
Prices, current releases and advisories checked November 8, 2026; packaging and unchanged licence evidence from October 19, 2026: ISC downloads and support dates, BIND 9.20 release notes, Knot DNS downloads, validns releases, Debian’s record of CVE-2026-39155, Debian and Ubuntu package records, and Homebrew records for bind, knot.
Earlier hands-on check, October 3, 2026
Show 1 criteria
| Feature | named-checkzone | named-compilezone | kzonecheck | validns |
|---|---|---|---|---|
| Earlier hands-on check, October 3, 2026 (historical) | 9.18.39 with -i local: rejected an invalid address and a CNAME conflict (exit 1); warned about a missing MX target address and missing glue, then printed OK and exited 0 | Not part of the check | 3.3.4: rejected the invalid address, the CNAME conflict and the missing glue (exit 1); accepted the missing MX target address silently | 2017 package with -p all rejected even the intact file (one NS). 0.11.0 build with selected policies accepted the intact file and rejected the invalid address, CNAME conflict and missing glue; missed the missing MX target address |
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 Ubuntu 24.04, run on October 3, 2026, before Practical Picks adopted its research-only method later that day. Five synthetic zone files for an invented domain; Ubuntu packages and one task-local validns 0.11.0 build. It did not decide any recommendation. Earlier check record, October 3, 2026.
What matters when choosing
named-checkzone is our Preferred Pick for checking a BIND-style zone file on your own computer before you upload it to a DNS host. It comes with BIND from ISC and documents the widest set of checks here. Besides syntax errors and a CNAME that shares a name with other records, it checks that MX, SRV and delegation NS records point to names that have addresses, that a delegated child has the glue records it needs, and it warns when an MX or SRV record points to a CNAME or a wildcard is used in an unusual place. ISC maintains it in BIND 9.20, the current stable branch, which ISC supports until the second quarter of 2028; 9.20.30 came out on October 21, 2026. It is free under the MPL 2.0 and packaged for Linux, BSD and macOS. Run it with -i local to keep the check on your computer: in its default full mode it also looks up names outside your zone through your computer’s DNS resolver. ISC named-checkzone manual, BIND versions and support dates
Read every line of its output, not just the exit code. A missing address for an MX target, or missing glue for a child zone, is reported as a warning: named-checkzone still prints OK and exits with status 0. Its manual offers no setting that turns these warnings into failures; an ISC engineer logged a feature request for one in 2009, and the current manual still has none. Its quiet mode, -q, prints nothing and reports only the exit status, so it hides them. A script that uploads whenever the exit status is 0 would therefore upload a file with these problems. Keep it updated too: BIND 9.20.23 and 9.18.49, released May 20, 2026, fixed a bug that silently skipped the missing-glue check for a name server that had already drawn a warning about extra AAAA glue. 2009 ISC reply, ISC’s glue-check fix
Choose kzonecheck instead if a script must stop on any problem, or if your zone is already DNSSEC-signed. Knot DNS’s checker, from CZ.NIC, exits with an error on every finding, including missing glue, and checks DNSSEC signatures. Its documented checks do not cover MX, SRV or NS targets, though, so a mail server name with no address passes. Knot’s semantic checks, kzonecheck manual
validns is narrower; named-compilezone needs more configuration. validns reports problems by file line and checks DNSSEC chains thoroughly, but its CNAME and glue checks must be switched on one by one, its own documentation warns that it can report a valid zone as faulty, and most distribution packages predate its July 2026 release, which fixed buffer overflows in its zone-file parser. named-compilezone can run BIND’s integrity checks too, but they are disabled by default and it requires an output file. Choose named-checkzone for a check before upload. validns README
named-checkzone leads narrowly: 4.10 against named-compilezone’s 4.00. Both offer BIND’s checks; named-checkzone needs fewer settings for this job. BIND manuals, checked November 8, 2026
A clean result is not a guarantee. None of these tools can tell you whether your DNS host will accept the file, whether the parent zone delegates to the right servers, or whether mail will be delivered. Check your host’s import rules as well.
No Rising Star selected. bindlint is a promising linter with line-numbered explanations and a setting that makes warnings fail the run. We have not established that it runs on both Windows and macOS, so it does not qualify for the award in this comparison. bindlint documentation, checked November 8, 2026
named-checkzone
Preferred Pick · read every warning before upload
Choose named-checkzone to check a BIND-style zone file on your own computer before uploading it. Run it with -i local to avoid network lookups, and read every line: missing MX target addresses and missing glue are warnings that still end in OK and exit status 0.
Reasons to choose it
- Widest documented checks here, including MX, SRV and NS targets and required glue
- Maintained by ISC in BIND 9.20, supported until Q2 2028
- Packaged without the DNS server on Debian and Ubuntu; Homebrew on macOS
What to watch
- Missing addresses and glue never change the exit status; -q hides them
- Default full mode looks up names outside your zone through your resolver
- Glue check could be skipped before 9.20.23 and 9.18.49 (May 2026); no native Windows build
named-checkzone “checks the syntax and integrity of a zone file” and “performs the same checks as named does when loading a zone”, according to ISC’s manual for BIND 9.20. A record it cannot read, such as an invalid IPv4 address, or a CNAME that shares its name with other records stops the load, and the command exits with status 1. Its integrity checks are set with -i. The default, full, checks that MX, SRV and delegation NS records point to names with A or AAAA records, both inside and outside your zone, and that glue in your zone matches what the child zone advertises. local checks only names inside your zone and that required glue exists for a name server inside a delegated child. To check names outside the zone, BIND’s source code looks them up through your system’s resolver, so full needs a network connection and sends those names to your resolver. Further options warn about MX or NS records written as addresses, MX or SRV records that point to a CNAME, host names with invalid characters, non-terminal wildcards, and TTLs above a limit you set. named-checkzone manual, BIND checking code
The manual says only that the command “returns an exit status of 1 if errors were detected and 0 otherwise”. Missing addresses and missing glue count as warnings, not errors, and no option changes that: the -m and -n modes concern MX and NS records written as IP addresses, not targets without addresses. Stéphane Bortzmeyer raised this on a DNS operators’ list in October 2009, and ISC’s Cathy Almond replied that she had logged a feature request for an “enhanced exit status” option; the BIND 9.20 manual has no such option. If you automate the check, search the output for “has no address records” and “REQUIRED GLUE” as well as testing the exit status. Before BIND 9.20.23 and 9.18.49 (May 20, 2026), a coding error made named-checkzone skip the missing-glue check for any name server that had already triggered an extra-AAAA-glue warning, so a zone missing required A glue could pass. 2009 thread, ISC merge request 11899, BIND 9.20 release notes
Read the full named-checkzone analysis and sources
BIND is free under the Mozilla Public License 2.0. ISC lists 9.20 as the current stable, extended-support branch, supported until the second quarter of 2028, and marks 9.18 as end of life since its last release, 9.18.50, in June 2026. Debian and Ubuntu put named-checkzone in the bind9-utils package, so you do not need to install the DNS server itself; Homebrew’s bind formula, at 9.20.29 on October 19, 2026, recorded about 17,400 installs in the 12 months to October 19, 2026. Ubuntu 24.04 still ships 9.18.39 with Ubuntu’s own security updates (latest October 14, 2026); that version predates ISC’s glue-check fix, and we did not establish whether Ubuntu has applied it. ISC dropped Windows with BIND 9.16, so on Windows you need the Windows Subsystem for Linux. ISC fixed 34 BIND security flaws in releases from January 21 to September 16, 2026, 14 of them in 9.20.29, and fixed four more in 9.20.30 on October 21. Their descriptions concern the named server and the DNS messages it handles; none names named-checkzone. BIND downloads and support dates, BIND 9.20 release notes, BIND 9.20.30 notes, checked November 8, 2026, Homebrew bind, ISC on Windows support
In an earlier hands-on check on October 3, 2026, before we adopted our research-only method, Ubuntu’s named-checkzone 9.18.39 read five small synthetic zone files with -i local. It accepted the intact file and rejected an invalid address and a CNAME conflict with exit status 1, naming the file line. For a missing MX target address and missing child glue it printed a warning naming the record, then OK, and exited 0, which is the behaviour described above. The files had no AAAA glue, the condition behind the bug fixed in May 2026. The check did not cover full mode, DNSSEC, larger zones or other systems, and it did not decide this recommendation. Earlier check record, October 3, 2026
Used named-checkzone? Share your experience to help other readers choose.
named-compilezone
Convert and check · configure integrity checks first
Consider named-compilezone when you also need a converted zone file. For a check before upload, named-checkzone needs fewer settings and leads narrowly, 4.10 to 4.00.
Reasons to choose it
- Can run the same local target and glue checks as named-checkzone
- Converts to text or BIND raw format
- Shares BIND packaging and ISC maintenance
What to watch
- Integrity checks default to none; set -i local and the other checks you need
- Requires -o output; read warnings as well as checking the exit status
- No native Windows build
named-compilezone comes with BIND and checks a zone file’s syntax and integrity while writing a converted copy. Its manual documents the same local MX, SRV and delegation NS target checks and required-glue checks as named-checkzone, but its integrity mode defaults to none. Set -i local for those checks without looking up external names. Name checks, alias warnings and several other checks also default to being ignored. The manual recommends running named-checkzone first when the output must meet BIND’s default requirements. BIND named-compilezone manual, checked November 8, 2026
Choose it if conversion is part of your work and you are prepared to configure the checks explicitly. It requires -o to name the output file, or -o - for standard output, and returns 1 for errors and 0 otherwise; integrity warnings still need reading. It adds no checking advantage for someone who only wants to inspect a file before upload, which is why named-checkzone is our Pick. Both are free under MPL 2.0 and share BIND’s packaging, maintenance and security record. The current stable release is 9.20.30, released October 21, 2026. ISC downloads, BIND release notes, checked November 8, 2026.
Used named-compilezone? Share your experience to help other readers choose.
kzonecheck
Also consider · fail on any finding, or a signed zone
Consider kzonecheck when a script must stop on every problem, or when your zone file is already DNSSEC-signed. Check MX, SRV and NS targets another way: it does not check that they have addresses.
Reasons to choose it
- Every finding, including missing glue, gives a non-zero exit status
- Validates DNSSEC signatures and ZONEMD digests
- Maintained by CZ.NIC; 3.6.2 released October 21, 2026
What to watch
- No check that MX, SRV or NS targets have addresses
- Older packages predate a 2025 fix for a false missing-glue warning
- Linux, BSD and macOS only
kzonecheck “checks zone file syntax and runs semantic checks on the zone content”, the same checks Knot DNS’s server runs. Knot’s reference lists them. Mandatory checks cover a missing SOA record, a CNAME with other records or more than one CNAME at a name, DNAME rules, and a DS record at the zone apex. Extra checks cover a missing NS record at the apex, missing glue, invalid DS or NSEC3PARAM records, CDS and CDNSKEY consistency and DNSSEC validation. kzonecheck checks DNSSEC records automatically when the SOA record is signed, and -z verifies a ZONEMD digest. Its manual says any exit status other than 0 means an error, and its source code sets an error status whenever a check reports a finding, including extra checks such as missing glue. kzonecheck manual, Knot semantic checks, kzonecheck source
The documented list has no check that MX, SRV or NS targets have addresses, so an MX record pointing to a name with no A or AAAA record passes. Knot 3.4.7, released June 4, 2025, fixed a false missing-glue warning when a name server sits under another delegation; kzonecheck runs the server’s checks, and older packages, such as Ubuntu 24.04’s 3.3.4 and Debian 13’s 3.4.6, predate that fix. Knot 3.5.8, released September 4, 2026, fixed kzonecheck’s detection of the zone origin when the file name is short; giving the origin with -o avoids the question. Knot release history
Read the full kzonecheck analysis and sources
Knot DNS is free under the GPL version 2 or later since 3.5.0 (September 2025); earlier versions, including Ubuntu 24.04’s 3.3.4, used version 3 or later. CZ.NIC released 3.6.2 on October 21, 2026, supported until the third quarter of 2028, and keeps 3.5.10 as the previous stable branch until the third quarter of 2027. Debian and Ubuntu ship kzonecheck in the knot-dnssecutils package, separate from the server; CZ.NIC also publishes its own Debian, Ubuntu and RPM packages, and Homebrew’s knot formula recorded about 3,000 installs in the 12 months to October 19, 2026. Knot targets Linux, BSD and macOS, not Windows. The one Knot DNS advisory we found from 2026, CVE-2026-39155, concerns the server’s online-signing module, not kzonecheck. Knot DNS downloads, licence, Homebrew knot, Debian record of CVE-2026-39155
In an earlier hands-on check on October 3, 2026, before we adopted our research-only method, Ubuntu’s kzonecheck 3.3.4 read the same five synthetic files with -o pp284.test.. It accepted the intact file and exited 1 for the invalid address, the CNAME conflict and the missing child glue, naming the owner in the last two. For the invalid address it printed only “failed to run semantic checks (failed)”, without the file line. It accepted the file whose MX target had no address and printed nothing, as its documented check list predicts. Earlier check record, October 3, 2026
Used kzonecheck? Share your experience to help other readers choose.
validns
Strict DNSSEC and policy checks · version 0.11 only
Consider validns for line-numbered reports and thorough DNSSEC chain checks if you can install 0.11.0 and are prepared to choose its policy checks yourself.
Reasons to choose it
- Reports every problem with the file line; non-zero exit on any error
- Thorough DNSSEC signature and NSEC/NSEC3 chain checks
- Revived by DNS-OARC: three releases in 2026
What to watch
- CNAME and glue checks are off unless you select those policies
- Its README warns that valid zones can be reported as faulty
- Most distribution packages predate the July 2026 parser overflow fix
validns, from DNS-OARC, reads a zone file and “performs a series of structural, consistency, and - for signed zones - DNSSEC checks”. Basic checks always run: every record must parse, there must be one SOA record and it must come first, records must be inside the zone, and TTLs must match within a record set. For signed zones it verifies every signature and walks the NSEC or NSEC3 chain. Other checks are policies you switch on with -p, including cname-other-data, mx-alias, ns-alias, and, since 0.11.0, missing-glue and occluded-records. Without them, a CNAME conflict is not reported. -p all also turns on single-ns, which requires at least two NS records per name. It exits with a non-zero status if it reported any error, and its source code starts each message with the file name and line number. validns README, 0.11.0 release notes, message format in the source
Its README is candid about limits: “it should be possible (and easy) to construct a perfectly valid zone file which validns will report as problematic”, and text in TXT and HINFO records must be in double quotes. BIND’s $GENERATE directive is only partly supported: the parser rejects a step value and the offset and width modifiers, and a request for full support has been open since May 2026. It has no check that MX or SRV targets have addresses. validns README, directive parser, open issue 123
Read the full validns analysis and sources
Anton Berezin started validns in 2011. After version 0.8.0 in February 2014 there was no release for almost 12 years. DNS-OARC then took it on: the project moved to Codeberg, its GitHub repository was archived on February 4, 2026, and 0.9.0 (January 30, 2026), 0.10.0 (May 18) and 0.11.0 (July 15) followed. On October 19, 2026, we counted 199 commits that year, all by Anton Berezin and Jerry Lundström; the repository showed further development when checked on November 8, 2026. Version 0.11.0 fixed a buffer overflow when parsing overlong quoted strings, along with crashes, a data race and memory leaks. Most distributions still ship older code: Ubuntu 24.04 a 2017 snapshot, Debian 13 a 2023 snapshot and Ubuntu 26.04 version 0.9.0. Debian testing and Ubuntu 26.10 carry 0.11.0, and DNS-OARC publishes its own validns packages for Debian, SUSE and openSUSE through the openSUSE Build Service. There is no Homebrew formula, and building it needs the Judy library. It is free under a two-clause BSD licence. validns releases, archived GitHub repository, DNS-OARC packages, Debian package
In an earlier hands-on check on October 3, 2026, before we adopted our research-only method, Ubuntu’s 2017 validns package with -p all rejected even the intact synthetic file because it had one name server, as the single-ns policy requires. With the CNAME and alias policies only, it rejected the invalid address and the CNAME conflict, naming the file line, and missed the missing glue. A task-local build of 0.11.0 with the missing-glue policy also rejected the missing glue, naming the file line. Neither version reported the missing MX target address. Earlier check record, October 3, 2026
Used validns? 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 exit-status gap in named-checkzone is old and known. In October 2009, on the DNS-OARC operators’ list, Stéphane Bortzmeyer pointed out that named-checkzone reports a name server without an address but “does not set the return code > 0, so you have to test the output”, and asked for an option to make every warning fatal. ISC’s Cathy Almond replied that she had logged a feature request. BIND’s current manual still has no such option. 2009 thread
In February 2024 a Knot DNS user asked for kzonecheck to warn about records written without an owner name, which inherit the previous record’s name and can silently move if the file is reordered; the user had been “burned” by such a mistake. CZ.NIC closed the request in March 2025; we did not establish whether a warning was added. It is a reminder that a file can pass every check here and still not say what you meant. Knot issue 920
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 manual and reference documentation, release notes and release dates, source code where the manuals are silent, issue trackers and mailing lists, security advisories from the projects, OSV and Debian’s security tracker, and package records from Debian, Ubuntu and Homebrew, read on October 19, 2026. No project supplied access or payment, and our links carry no affiliate tracking.
This article first appeared on October 3, 2026, and then rested on a small hands-on check run that day, before we adopted our research-only method later that day. We keep that check as a dated observation. On Ubuntu 24.04, named-checkzone 9.18.39, kzonecheck 3.3.4, Ubuntu’s 2017 validns package and a task-local build of validns 0.11.0 each read five synthetic zone files for an invented domain: one intact, and one each with an invalid address, a missing MX target address, a CNAME conflict and missing child glue. The check shows what happened once in that setup, not how the tools behave on real or larger zones, and it did not decide any recommendation here. Each product section above says what it saw. Earlier check record, October 3, 2026
We wrote this for someone who edits a BIND-style zone file by hand and wants to catch mistakes on their own computer before uploading it to a DNS host. Before scoring, we fixed four criteria and their weights: check coverage, meaning which syntax and structural problems each tool documents that it catches (35%); clarity of results, meaning how findings are located and whether they change the exit status (20%); maintenance and security (25%); and setup and documentation (20%). All four tools are free, so cost carried no weight. On our five-point scale named-checkzone scored 4.10, named-compilezone 4.00, kzonecheck 3.75 and validns 3.10. The lead is narrow: named-compilezone offers the same checks once configured, but requires more setup. named-checkzone stayed ahead when we gave clarity 35% and when we gave maintenance 40%. kzonecheck came out ahead when we judged clarity only by whether every finding fails the run and weighted it heavily, and when we scored DNSSEC signature checks as part of coverage for a signed zone; those are the two uses we name for it in our assessment.
We checked that every widely used option for this reader was either compared or set aside for a stated reason, and now include named-compilezone, whose configurable integrity checks make it a suitable alternative. nsd-checkzone scored 2.63: it catches syntax errors and CNAME conflicts but not missing glue or target addresses. NSD 4.15.4, released October 21, 2026, is current; use 4.15.3 or later to avoid the four zone-parser flaws fixed on October 14. NSD downloads, security advisories, checked November 8, 2026.
NLnet Labs’ ldns tools read and print a zone (ldns-read-zone) or verify a DNSSEC-signed one (ldns-verify-zone) without the structural checks this job needs, and NLnet Labs’ newer dnst toolkit has no zone-checking command. PowerDNS’s pdnsutil zone check checks a zone already stored in a PowerDNS database, so you would first have to load your file into one. dnspython is a Python library, not a checker: when it reads a zone it checks only for SOA and NS records at the top, and since version 2.2 it resolves a CNAME conflict silently by keeping whichever record came last. Zonemaster tests a delegation by querying name servers, a different job from checking a file before upload. Browser-based zone linters ask you to paste your zone into a website, and DNS-as-code tools such as DNSControl and octoDNS check their own configuration formats.
We searched GitHub, Hacker News, package registries and recent reporting in October, then checked GitHub’s DNS, zonefile and DNS-tools directories on November 8, 2026. bindlint’s initial public source release is dated September 27, 2026. Its documentation supports local linting and configurable failure thresholds, with a score of 3.03 under the same criteria; the absence of independent reviews does not disqualify it. Its documented limits include not following included files, no DNSSEC validation and glue consistency checks still on the roadmap. Its Windows and macOS support remains unconfirmed, so no Rising Star is selected. The workflow and CLI directory listings do not establish platform support.
Six other linter repositories returned 404 in October and could not be checked again. The directories also listed zoneskein, a browser-first workbench, and editor extensions, which do not establish a command-line alternative for this job. bindlint, commit history, workflow directory, CLI directory, DNS directory, zonefile directory, DNS-tools directory, checked November 8, 2026.
| Tool | Public sources | What remains uncertain |
|---|---|---|
| named-checkzone | BIND 9.20 manual and release notes, ISC download and support page, ISC merge request 11899, BIND checking source code, 2009 operators’ list thread, ISC Windows notice, Debian, Ubuntu and Homebrew records. | Whether Ubuntu 24.04’s 9.18.39 package carries the May 2026 glue-check fix; exact output wording in 9.20. |
| kzonecheck | kzonecheck manual, Knot configuration reference, kzonecheck source code, Knot release history and downloads page, Knot issue tracker, Debian and Homebrew records, CVE-2026-39155 record. | How syntax errors are reported in current versions; whether the 2025 false-glue fix reached older distribution packages. |
| validns | README, release notes and changelog, licence, issue tracker, archived GitHub repository, DNS-OARC package page, Debian and Ubuntu records. | How often it rejects valid real-world zones; whether DNS-OARC’s two maintainers keep the current pace. |
| named-compilezone | BIND manual, download page and 9.20.30 release notes, checked November 8, 2026. | It requires explicit check settings and a converted output; warnings still need reading. |
| Newcomer assessment | bindlint documentation, commit history, security pages and GitHub directories, checked November 8, 2026. | Windows and macOS support is unconfirmed; no qualifying newcomer recommendation is established. |
None of these sources measures how often a checker misses a real problem or flags a correct file. Next substantive review is due January 17, 2027, or sooner if a release changes a check or a security advisory affects one of these checkers. Found a change? Contact the editors.
Sources and evidence
Checked November 8, 2026: BIND manuals, ISC downloads, BIND 9.20.30 release notes, ISC vulnerability matrix, Knot downloads, Knot security tracker, validns repository, licence, releases, NSD downloads, NSD advisories, and the bindlint and discovery links above. These update prices, releases, security findings and newcomer coverage; the unchanged evidence below remains dated October 19.
Checked October 19, 2026: BIND named-checkzone manual, downloads and support dates, 9.20 release notes, merge request 11899, checking source code, 9.16 end-of-life notice, October 2026 pre-announcement and Homebrew bind; the 2009 DNS-OARC operators’ thread; Knot DNS kzonecheck manual, semantic checks, kzonecheck source, release history, downloads, licence, issue 920, Homebrew knot and Debian record of CVE-2026-39155; validns repository and README, releases, 0.11.0 release notes, issue 123, source code for its message format and directives, archived GitHub repository, DNS-OARC packages and Debian package; NSD nsd-checkzone manual, zone-loading source, security advisories, 4.15.3 release and Homebrew nsd; and the earlier check record, October 3, 2026. No project supplied access or influenced the conclusion. No affiliate links were used. Recheck releases, advisories and package versions before any public release.
No screenshots are shown: these are command-line tools, and this comparison is based on public sources. The earlier check record, October 3, 2026 keeps the synthetic zone files and outputs from a small check run before our research-only method.