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
  • #1897
Closed
Open
Issue created May 28, 2020 by Brian Conry@bconryContributor

max-transfer-time-* and max-transfer-idle-* broken since 9.15.6

In 53f0b6c3 ("convert ns_client and related objects to use netmgr"), the logic for setting a timer to enforce max-transfer-time-out and max-transfer-idle-out was removed.

In 49d53a4a ("use netmgr for xfrin"), the max-transfer-time-in and max-transfer-idle-in options have met a similar destiny.

Edited Feb 02, 2022 by Ondřej Surý
Assignee
Assign to
Time tracking