Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 532
    • Issues 532
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 101
    • Merge requests 101
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • 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 Projects
  • BINDBIND
  • Issues
  • #3046

Closed
Open
Created Dec 06, 2021 by Mark Andrews@markaOwner

TCP client not being identified in log message

I was trying to match expected log messages in a system test (!5616 (merged)) and switching from UDP to TCP to force a SERVFAIL rather than timeout response resulted in <unknown> for the client being logged instead of IP address and port.

06-Dec-2021 16:26:06.430 DNS format error from 10.53.0.8#5300 resolving tcpalso.no-questions/A for <unknown>: empty question section, accepting it anyway as TC=1

The string I was expecting to match against was

resolving tcpalso.no-questions/A for 10.53.0.5#[0-9]*: empty question section, accepting it anyway as TC=1

I haven't checked 9.16 yet.

Edited Dec 06, 2021 by Mark Andrews
Assignee
Assign to
Time tracking