Network · Made a little simpler

DNS Zone File Validator

Inspect BIND-style zone text, relative owners, TTLs, apex SOA and NS records, and serial changes before deploying DNS configuration.

Free to useNo account neededProcessed on your device
Your workspaceProcessed on your device

Add this tool to your website

Paste this code into your page to add the tool and a visible ToolMellow credit link.

HTML embed code
Preview embed

DNS Zone File Validator: how to use it

  1. Paste or open a zone file. Use an explicit Zone origin or a $ORIGIN directive.
  2. Optionally enter the previous SOA serial. Select Validate BIND zone.
  3. Review findings and the interpreted record fields. Download the JSON report alongside the zone.

Limits and notes

Up to 128 KiB and 2,000 records. Supported Internet-class types: A, AAAA, CNAME, NS, PTR, MX, TXT, SOA, SRV, and CAA. Supports $ORIGIN, $TTL, comments, inherited owners and parenthesized continuations. Expand $INCLUDE and $GENERATE before reviewing them.

How your privacy works →

DNS Zone File Validator: common questions

Does a serial have to look like a date?

A valid SOA serial is an unsigned 32-bit integer. Date-like serials are a naming convention. The optional comparison uses RFC 1982 serial arithmetic.

How are relative names interpreted?

A relative owner or target uses the active origin. A final dot marks an absolute name. An indented owner inherits the previous owner.

What happens to unsupported records and directives?

The report identifies the line and marks it unvalidated. Check unsupported syntax in the tools for your deployment.

Guides