Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
BIND
BIND
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 633
    • Issues 633
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 104
    • Merge Requests 104
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ISC Open Source Projects
  • BINDBIND
  • Merge Requests
  • !2168

Merged
Opened Jul 21, 2019 by Evan Hunt@eachOwner

dig/delv/mdig +yaml output

  • Overview 11
  • Commits 6
  • Pipelines 7
  • Changes 23
  • YAML output containing multiple messages (i.e., multiple queries and responses) is now implemented as a list, because Paul found that otherwise he couldn't parse more than one object from a stream. dnstap-read -y doesn't do this, which causes me to wonder if it's broken, but nobody's complained.dig +qr will emit both query and response messages. mdig doesn't support +qr so it only emits response messages. delv only supports one QNAME at a time, so it only emits one record, not a list.
  • dig +yaml and delv +yaml output are modeled on dnstap-read -y, with a few differences:
    • the identity and version fields come from the frame stream and make no sense here
    • there's no DNSTAP message type (e.g., CQ or RR or whatever)
    • only the query_message_data/response_message_data sections are included, not the query_message or response_message sections, because those are basically identical to the existing output of dig, and I reckon if that's what someone needs, then they can just run dig.

Closes #1145 (closed)

Edited Jul 25, 2019 by Evan Hunt
Assignee
Assign to
Reviewer
Request review from
BIND 9.15.4
Milestone
BIND 9.15.4 (Past due)
Assign milestone
Time tracking
Reference: isc-projects/bind9!2168
Source branch: each-dig-yaml

Revert this merge request

This will create a new commit in order to revert the existing changes.

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.

Cherry-pick this merge request

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.