DNS Record Parser

Parsed 4 record(s) with 0 problem line(s).

How it works

• Split the input into lines and strip `;` / `#` comments.
• Read the optional TTL and IN class, then the record type.
• Parse the record value, including MX preference and quoted TXT data.
• Report any line that does not match a supported record with its line number.

• Parsing is entirely local and makes no network request.

Methodology

1. Tokenize each non-comment line into name, optional TTL, optional IN class, type and value.
2. Validate each value against its record type and report a 1-based line number for failures.
3. Re-serialize the parsed records in canonical zone-file form to prove the round trip.

Usage

1. Paste zone-file lines or the answer section of a `dig` response.
2. Run the parser; each line becomes one record or one positioned error.
3. Copy the normalized zone-file output if you need a clean version.

Examples

These are examples, not current values: they use fixed inputs, while the interactive tool computes live results in your browser.

Zone-file records

{
  "text": "example.com. 3600 IN A 93.184.216.34\nwww 300 IN CNAME example.com.\nexample.com. IN MX 10 mail.example.com.\nexample.com. 60 IN TXT \"v=spf1 -all\""
}

dig answer section

{
  "text": "example.com.\t3600\tIN\tNS\ta.iana-servers.net.\nexample.com.\t3600\tIN\tNS\tb.iana-servers.net."
}

Limitations

Privacy

This tool is browser-only. The text you paste is parsed locally and is never uploaded, stored or logged.