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 576
    • Issues 576
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 111
    • Merge requests 111
  • 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
  • #2589
Closed
Open
Issue created Mar 18, 2021 by Ondřej Surý@ondrejOwner0 of 1 checklist item completed0/1 checklist item

Follow-up from "Resolve "memory leak when named attempts to listen on FreeBSD virtual interface""

The following discussion from !4823 (merged) should be addressed:

  • @sgoldlust started a discussion:

    - If an outgoing packet exceeded max-udp-size, it was dropped instead
      of sending a proper response. To address this issue, the IP_DONTFRAG settings on
      UDP sockets, which were enabled during DNS Flag Day 2020, were rolled back.
Assignee
Assign to
Time tracking