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 569
    • Issues 569
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 112
    • Merge requests 112
  • 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
  • #564
Closed
Open
Issue created Sep 28, 2018 by Michał Kępień@michalOwner

Mirror zone configuration tweaks and cleanups

Various discussions around mirror zones which happened after they were initially implemented (see #342 (closed), #375 (closed)/!475 (closed), Twitter poll) indicate that certain aspects of mirror zone configuration could use some tweaks:

  • type secondary; mirror yes; should be replaced with type mirror;
  • it should be clearly documented that:
    • mirror zones are supposed to replace the configuration example provided by RFC 7706 rather than augment it,
    • mirror zones only work the intended way if recursion is available in the view they are configured in,
    • by default, outgoing transfers of mirror zones are disabled.

Furthermore:

  • the list of valid mirror zone options should be trimmed down,
  • NOTIFY configuration for mirror zones is a bit too hacky and could use some love,
  • we currently do not test whether mirror zones can be added and removed dynamically (using rndc).

The above concerns need to be addressed before we release BIND 9.14 and since configuration changes are involved, BIND 9.13.4 would be the more appropriate target.

Assignee
Assign to
Time tracking