Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 603
    • Issues 603
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 87
    • Merge requests 87
  • 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
  • #3242
Closed
Open
Issue created Mar 30, 2022 by Tony Finch@fanfDeveloper

Excessive notify traffic

support ticket #20530 reports excessive NOTIFY traffic after an upgrade from 9.16 to 9.18.

I have reproduced this behaviour on a test VM: all it requires is a non-responsive NOTIFY recipient. It appears that the overall request timeout is not being applied.

@marka has a patch https://support.isc.org/Ticket/Attachment/773740/500542/set-udpretries-patch.txt

There are a number of other similar patterns in zone.c related to DS checking and NS queries, which presumably have the same problem.

This regression was introduced by !4601 (merged) (use netmgr for dispatch). I have not pinned down exactly the point in that branch where it stops working because there is other breakage that makes it difficult.

Edited Mar 31, 2022 by Tony Finch
Assignee
Assign to
Time tracking