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 611
    • Issues 611
    • 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
  • #3380
Closed
Open
Issue created May 25, 2022 by Tomas Velech@velechac

member zones are deleted if RRsig appears in the catalog zone

If RRsig appears in the catalog zone, all member zones are immediately deleted. Affected version is Bind 9.16

general: warning: catz: unknown record in catalog zone - ff558fb7a97903f2e4ad534c6a6453b6139adefd.zones.prod-public.catalog IN RRSIG(failure) - ignoring
general: info: catz: deleting zone ‚example.com‘ from catalog 'prod-public.catalog' - success
general: warning: catz: catz_delzone_taskaction: zone ‚example.com‘ deleted

Note from QA: The labels on this issue are confusing because its history is confusing, too. This problem also affected BIND 9.18+ in the recent past, but it was inadvertently addressed by commit 0b2d5490 (part of !6012 (merged), merged in May 2022). The problem is that we did not recognize at the time that that commit fixes the issue which was reported here (only subsequently, and for BIND 9.16) and therefore we did not announce that in the release notes for May 2022 releases. The net result is that even though this issue is not labeled with the Affects v9.19 and Affects v9.18 labels, the release note for this issue was put into all June 2022 releases despite the fact that the problem was already solved in BIND 9.18+ back in May 2022. In other words, a bit of historical accuracy has been sacrificed in exchange for preventing confusion (to some extent).

Edited Jul 07, 2022 by Michał Kępień
Assignee
Assign to
Time tracking