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 610
    • Issues 610
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 87
    • Merge requests 87
  • 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
  • #3225
Closed
Open
Issue created Mar 23, 2022 by Arаm Sаrgsyаn@aramDeveloper

[5/5] Catalog zones member zone reset documentation

The DNS catalog zones draft version 5 document requires that catalog zone consumers must reset the member zone's internal zone state when its unique label changes (either within the same catalog zone or during change of ownership performed using the "coo" property).

BIND already behaves like that, and, in fact, doesn't support keeping the zone state during change of ownership even if the unique label has been kept the same, because BIND always removes the member zone and adds it back during unique label renaming or change of ownership.

BIND should document the described behavior and add a log message to inform when unique label renaming occurs.

Edited Apr 26, 2022 by Michał Kępień
Assignee
Assign to
Time tracking