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 610
    • Issues 610
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 114
    • Merge Requests 114
  • 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
  • Issues
  • #1206

Closed
Open
Opened Sep 03, 2019 by Michael McNally@McNallyDeveloper

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
November 2019 (9.11.13, 9.14.8, 9.15.6)
Milestone
November 2019 (9.11.13, 9.14.8, 9.15.6) (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: isc-projects/bind9#1206