Supported DNS Zone Source Workbench
Expand supplied DNS master-file names and defaults, inspect selected IN record wire fields, and download an explicit canonical zone fixture.
Loading tool…
How to use Supported DNS Zone Source Workbench
Expand supplied DNS master-file names and defaults, inspect selected IN record wire fields, and download an explicit canonical zone fixture. Follow $ORIGIN, $TTL and omitted-owner source witnesses without sending DNS queries. Ten common record types retain escaped octets and separate TXT character-strings.
- Provide optional ascii zone source file, ascii zone master-file source, initial absolute origin, optional initial decimal ttl.
- Choose the supported mode and run the tool. Review its assumptions and any reported errors.
- Copy the result or download a separate output; reset to clear the current form.
Good to know
- Selected ASCII-source master-file subset: A, AAAA, NS, CNAME, PTR, MX, TXT, SOA, SRV and CAA in class IN. $ORIGIN and $TTL are supported. $INCLUDE, $GENERATE, DNSSEC, unknown/generic TYPE records, non-IN classes and human-readable TTL units are refused; this is not a complete BIND/server-load validator.
- Source at most 100,000 bytes, 5,000 physical lines, 1,000 logical records/directives, 20,000 total tokens, 64 fields per record, 8,192 characters per token and 8 parenthesis levels. Direct Unicode source, BOM, controls, bare CR, quoted physical newlines, escaped physical continuation and quoted/unquoted token concatenation are outside the profile. Use ASCII escapes for arbitrary octets.
- Names are expanded without hostname policy or IDNA conversion: labels 1–63 octets and full names at most 255 wire octets. Relative names use the current origin; only an unescaped final dot is absolute. Escaped dots remain within labels. Omitted owners refer to the preceding expanded owner even after $ORIGIN changes.
- TTL/time values are decimal seconds no greater than 2,147,483,647; SOA serial is an unsigned 32-bit value. An explicit $TTL/initial default governs omitted TTLs; without one, the prior explicit record TTL is used. SOA minimum is not inferred as a default. At most 255 octets per TXT chunk and 1,024 per selected CAA value; CAA values have no artificial TXT length byte.
- Canonical output makes owners, domain-valued RDATA, TTL and IN explicit. Byte escapes and separate TXT chunks survive reinspection; source comments, original whitespace, source case for CAA tags and directive layout are not preserved. Canonical text is capped at 250,000 characters and reports at 500,000.
- No zone is installed, network request made, DNS answer trusted, DNSSEC verified or delegation/CNAME/issuer policy certified. Reserved CAA flag bits remain visible for review. A 10-second Worker preparation deadline is separate from the 2-second computation deadline.
- The formatted report is limited to 500,000 characters. Reduce the source when that output budget is exceeded.
- Inputs are processed on this device and are not automatically saved or uploaded.
Common questions
Does a successful report prove this zone can be published?
It proves only that the source fits the declared local parsing profile and that the selected fields can be expanded and encoded. Real authoritative servers and DNS policy require separate checks. The downloaded fixture is never installed or queried by this tool.
Does this change my original input?
No. The tool returns a separate result. Review that output before using it in another application.
Keep going with related tools
All developer →DNS Wire Message Workbench
Build an offline DNS query or inspect a bounded captured DNS wire message.
DeveloperDNSSEC DS Record Builder
Calculate SHA-256 or SHA-384 DS records from a public DNSKEY field, with canonical DNS owner bytes and a key tag.
DeveloperIP Subnet Workbench
Calculate exact IPv4/IPv6 CIDR bounds, address count and membership.