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 612
    • Issues 612
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 89
    • Merge requests 89
  • 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
  • #905
Closed
Open
Issue created Feb 27, 2019 by Michał Kępień@michalOwner

nsupdate does not honor the operating system's preferred ephemeral port range

While it is a bug in and of itself, IMHO the most compelling reason to fix this problem is that it is causing rare system test failures.

nsupdate may pick a source port number which clashes with a port number assigned to some named instance for listening. This does not trigger an error upon bind() because both nsupdate and named set SO_REUSEADDR for the relevant sockets. The end result is that nsupdate is unable to receive any responses to its queries and thus indicates a timeout.

Another possible symptom of this bug is a named instance refusing to start with an "address already in use" error - which is what happens if it tries to bind() to its configured listening port when some nsupdate process is already bound to that same port (as its source port).

Edited Feb 27, 2019 by Michał Kępień
Assignee
Assign to
Time tracking