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 637
    • Issues 637
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 104
    • Merge Requests 104
  • 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
  • #2349

Closed
Open
Opened Dec 15, 2020 by Cathy Almond@cathyaDeveloper

Should we back-port max-ixfr-ratio from 9.17 to earlier versions of BIND?

I can't see any other elegant option currently that could be used to 'protect' a zone hosting set-up from receipt and onward propagation of a massive IXFR to the service-providing authoritatives.

This happens sometimes accidentally (see Support Ticket #17366) and I would rather provide a solid solution in named, than encourage scripting that spots when something like this happens, and then goes off to delete .jnl or zone files on disk to prevent the same IXFR heading out to Internet-facing servers, where the effects of applying it can be seriously detrimental to server performance.

!3113 (merged) #1515 (closed)

Assignee
Assign to
February 2021 (9.11.28, 9.11.28-S1, 9.16.12, 9.16.12-S1, 9.17.10)
Milestone
February 2021 (9.11.28, 9.11.28-S1, 9.16.12, 9.16.12-S1, 9.17.10) (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: isc-projects/bind9#2349