Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 565
    • Issues 565
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 93
    • Merge requests 93
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • BINDBIND
  • Issues
  • #106
Closed
Open
Issue created Feb 23, 2018 by Vicky Risk@vickyDeveloper

[RT# 44978] dig feature to print unexpected reply messages

Mark,

I was wondering how difficult it would be to have an option where dig would parse DNS replies seen from the unexpected source for debugging purposes.

Example from the IETF network:

dig @75.75.75.75 +timeout=1 +retries=1000
;; reply from unexpected source: 69.241.23.140#53, expected 75.75.75.75#53
;; reply from unexpected source: 69.241.23.140#53, expected 75.75.75.75#53
;; reply from unexpected source: 69.241.23.152#53, expected 75.75.75.75#53
;; reply from unexpected source: 69.241.23.152#53, expected 75.75.75.75#53
;; reply from unexpected source: 69.241.23.150#53, expected 75.75.75.75#53
;; reply from unexpected source: 69.241.23.150#53, expected 75.75.75.75#53
;; reply from unexpected source: 69.241.23.148#53, expected 75.75.75.75#53
;; reply from unexpected source: 69.241.23.136#53, expected 75.75.75.75#53
;; reply from unexpected source: 69.241.23.136#53, expected 75.75.75.75#53

"Jared Mauch" jared@puck.nether.net

comment [Mark] Seems reasonable. Basically it would be a new flag then parse and print the response.

Testing would require a custom server that replies from a different address.

Edited Jul 11, 2018 by Mark Andrews
Assignee
Assign to
Time tracking