Skip to content
jc-rs
GitHub

dig

--digv2.5.0

Converts `dig` command output to JSON

commandslurpable
$ dig | jc-rs --dig

A real pair

From the reference corpus (osx-10.14.6/dig-noall-answer.json). The left pane is the input the fixture ships; the right pane is the corpus's expected JSON. CI compares jc-rs with it field by field under the published differential. Hover a value to see where it came from.

digosx-10.14.6
cnn.com.		47	IN	A	151.101.65.67
cnn.com.		47	IN	A	151.101.193.67
cnn.com.		47	IN	A	151.101.129.67
cnn.com.		47	IN	A	151.101.1.67
expected outputjson
Use the Left and Right arrow keys to highlight the matching value in the input.
[
  {
    "answer": [
      {
        "name": "cnn.com.",
        "class": "IN",
        "type": "A",
        "ttl": 47,
        "data": "151.101.65.67"
      },
      {
        "name": "cnn.com.",
        "class": "IN",
        "type": "A",
        "ttl": 47,
        "data": "151.101.193.67"
      },
      {
        "name": "cnn.com.",
        "class": "IN",
        "type": "A",
        "ttl": 47,
        "data": "151.101.129.67"
      },
      {
        "name": "cnn.com.",
        "class": "IN",
        "type": "A",
        "ttl": 47,
        "data": "151.101.1.67"
      }
    ]
  }
]

Fixture coverage

24/24oracle-valid pairs match under the published structural JSON comparison

Magic syntax

jc-rs digjc-rs runs the command itself and parses what it prints. Recognised for: `dig`

Source: crates/jc-rs-parsers/src/network/dig.rs. jc-rs targets the schemas defined by the original Python tool. Fixture coverage above is the measured evidence for this parser; test the inputs your pipeline depends on. Compare