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 570
    • Issues 570
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 98
    • Merge requests 98
  • 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
  • #1842
Closed
Open
Issue created May 13, 2020 by Cathy Almond@cathyaDeveloper

Correct the BIND ARM to say that the default session-key for use with 'update-policy local;' is generated at startup

The BIND ARM says:

A pre-defined update-policy rule can be switched on with the command update-policy local;. 
Switching on this rule in a zone causes named to generate a TSIG session key and place it in a file. 
That key will then be allowed to update the zone, if the update request is sent from local- host. 
By default, the session key is stored in the file /var/run/named/session.key; the key name
is "local-ddns" and the key algorithm is HMAC-SHA256. These values are configurable with the
session-keyfile, session-keyname and session-keyalg options, respectively).

This is not actually true - the session-key is generated when named starts up, irrespective of whether it's needed or not.

Assignee
Assign to
Time tracking