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 568
    • Issues 568
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 95
    • Merge requests 95
  • 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
  • #3707
Closed
Open
Issue created Nov 30, 2022 by Thib D@thibmac0241

named-checkzone change of behaviour in 9.16.35

Summary

Hello,

Not sure this is a bug of feature change, but since it wasn't mentioned in the changelog I believe this was not expected:

named-checkzone text output has changed in 9.16.35 (haven't tested on other new branches).

I believe this comes from this commit : 80e66fbd

BIND version used

9.16.35

Steps to reproduce

Run named-checkzone on a valid zone.

What is the current bug behavior?

With 9.16.35 :

named-checkzone example.com named.example.com
zone example.com/IN: loaded serial 2022113010
OK
zone example.com/IN: final reference detached

What is the expected correct behavior?

With 9.16.34 :

named-checkzone example.com named.example.com
zone example.com/IN: loaded serial 2022113010
OK

Not sure this line is relevant when performing a checkzone, and I'm pretty sure there are a few systems that use named-checkzone are parsing the output when running checkzones.

Best regards,

Thibaud

Edited Nov 30, 2022 by Thib D
Assignee
Assign to
Time tracking