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 522
    • Issues 522
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 99
    • Merge requests 99
  • 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
  • #1206

Closed
Open
Created Sep 03, 2019 by Michael McNally@McNally

Customer Feature Request: Add "high-water" measurement for tcp-clients

Since we changed tcp-clients limit enforcement in response to CVE-2018-5743, several customers have contacted us asking how to set limits appropriately.

Yoshitaka Aharen of M-root has offered what we think would be a useful suggestion which would help him and other operators who want to scale limits appropriately. He asks if named can keep track of a "high-water" limit for the number of simultaneous TCP clients, correctly pointing out that this is likely to be of more help to customers than random periodic polling via 'rndc status' which, if not performed frequently, could easily miss spikes in usage.

Related to Support #15134 and #15065

Assignee
Assign to
Time tracking