DNS Zone File Parser (BIND Format to Record Table)

Reads a BIND-style zone file and lists every record with its full name, TTL, class, type and data. It applies $ORIGIN and $TTL, joins multi-line records in parentheses and can print JSON.

Use the tool

Why this tool exists

Zone files are compact on purpose: a blank owner repeats the previous name, @ means the origin, and names without a trailing dot get the origin added. That makes them hard to read and easy to get wrong, for example by forgetting a dot.

The parser expands all of that so you can see what a server would load. It checks a few common mistakes (missing SOA, a CNAME next to other data). It does not support $INCLUDE or $GENERATE, and it does not validate record data.

How to use it

  1. Paste your zone file.
  2. Add an origin if the file has no $ORIGIN line.
  3. Read the table, or tick JSON for a machine-readable list.
  4. Check the notes below the table for missing SOA records or CNAME conflicts.

Frequently asked questions

Why does a name end with a dot?

A trailing dot marks a fully qualified name. The parser shows every owner name in that form.

What if a record has no TTL?

It uses the last $TTL, or the last explicit TTL in the file. If neither exists the TTL shows as a dash.

Are $INCLUDE and $GENERATE supported?

No. They are listed as not processed.

Does it check that the data is valid?

No. A type is checked against a list of known types, but the data is only split into fields.