DNS Zone-File Parser & Diff
Paste a zone file — or two — and read it as a record table, with the mistakes that take a domain offline flagged before you deploy.
A zone file is the authoritative text for a domain — and one wrong line takes it offline. Every DNS record for a domain lives in this one file: the SOA timers, the nameservers and their glue, the MX priorities, the CNAME aliases, the TXT records that carry SPF and DMARC. This parser reads a BIND zone file locally, shows every record as a filterable table, checks it against the rules that actually break DNS — a missing trailing dot, a CNAME sharing its owner, a serial nobody bumped, a nameserver with no glue — and diffs two versions so a one-line typo shows up before deployment, not after. Live answers live in the DNS lookup; the file on disk lives here. The companion article how to read a DNS zone file walks through the same records by hand.
Last updated:
Your zone files
Results
Validation findings
Record table
Diff: A → B
🔒 Your zone file never leaves your device. Parsing, validation and diffing run entirely in your browser — no upload, no server call, no account.
Zone-file anatomy — $ORIGIN, $TTL, SOA and the trailing dot
A zone file is a list of resource records, one per line (parentheses let one record span lines). Each record has an owner name, an optional TTL, a class — almost always IN — a type such as A or MX, and the record data. A line starting with whitespace inherits the previous owner; @ means the origin; a name without a trailing dot is relative and gets the current $ORIGIN appended. Comments start with a semicolon and run to the end of the line, except inside quoted strings.
$ORIGIN sets the origin that relative names resolve against; $TTL sets the default TTL for records that do not name one. A TTL is seconds, or a number with a unit — 30m, 1h, 2d, 1w. When neither $TTL nor an explicit TTL is given, a record falls back to the SOA minimum — and a record with no TTL anywhere is an error, not a silent default.
The SOA record is the zone’s control panel: mname is the primary nameserver, rname is the contact address (with the @ written as a dot), serial is the version number secondaries watch, refresh is how often a secondary checks for changes, retry is how long it waits after a failed check, expire is how long it keeps serving stale data when the primary is unreachable, and minimum is the default TTL and the negative-caching time. Bump the serial on every edit, or secondaries never pick the change up.
The trailing dot is the one character that breaks the most zones. A name ending in a dot is complete — mail.example.com. is exactly that host. A name without the dot is relative, so mail.example.com inside a zone with $ORIGIN example.com. silently becomes mail.example.com.example.com. — a host that does not exist. If a lookup ever returns a doubled domain, the missing dot is the first place to look.
What this parser does — and what it does not
It parses, validates and diffs — locally. It reads a BIND zone file into a record model, shows it as a table you can filter by type and search, checks it against the validation rules on this page, and diffs two versions record by record, with the SOA serial compared separately. Exports — record CSV, diff CSV and a canonical re-serialized zone file — are generated from the parsed model in your browser.
It does not query live DNS. It never asks a resolver anything: the answers it shows come from the file you gave it, not from the internet. A record can be perfect in the file and wrong in production (or the other way round) — check the live answers with the DNS lookup and the propagation checker.
It does not validate DNSSEC signatures, does not check parent-side delegation, and does not follow $INCLUDE. An $INCLUDE line is reported as a warning and its records are skipped — upload the included file’s records separately if you want them checked. Zone files can also list internal hostnames and addresses; that is exactly why this page never uploads them.
Be honest with yourself before you deploy a zone edit
A zone file that parses is not a zone file that works. The structure can be perfect while the meaning is wrong: a serial nobody bumped, a nameserver with no glue, an MX pointing at a name that only exists as a CNAME. Parsing tells you what the file says; the validation findings tell you where the file disagrees with the rules; only the live answers tell you what the internet sees.
The diff catches typos, not intent. It shows exactly which records changed between two versions — but it cannot tell you whether the change is the one you meant to make. Read the diff before you deploy, and keep the previous version: a one-line change to the wrong record is the classic way to take a domain offline.
Serial numbers are a convention, not a law. The YYYYMMDDnn form is a habit that makes versions readable, and this tool only ever notes a stale-looking one — it never errors on it. What matters is that the serial rises on every change; a serial that goes backwards can leave secondaries serving the old zone indefinitely.
What happens to your file
Nothing leaves your browser. The file or pasted text is parsed by JavaScript on this page: no upload, no server call, no storage, no account. Closing the page discards everything, including both zones and the diff.
Frequently asked questions
My zone file parses, but the domain still shows the old records — why?
Work through three suspects. First, did you bump the SOA serial? Secondaries only fetch a new copy when the serial rises. Second, TTL caching: resolvers that already cached the old answer keep serving it until the TTL expires. Third, check the live answers, not the file: the DNS lookup shows what resolvers return right now, and the DNS propagation checker shows the same query from many places at once.
Why does the parser warn about a missing trailing dot?
Because a name without the dot is relative, and the parser appends the current $ORIGIN to it. Inside a zone with $ORIGIN example.com., the bare name mail becomes mail.example.com. — usually what you want — but mail.example.com without the dot becomes mail.example.com.example.com., which is not. The warning shows the expanded form so you can see what the name actually became.
What does the diff count as "changed"?
A record whose owner, type and rdata match but whose TTL differs, or a single record at an owner and type whose value changed — for example www changing from one A address to another. Records that only exist in one version are added or removed, and the SOA serial is compared on its own line, because a serial bump is a version change, not a record change.