Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 528
    • Issues 528
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 103
    • Merge requests 103
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • 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 Projects
  • BINDBIND
  • Issues
  • #2906

Closed
Open
Created Sep 15, 2021 by Egbert@egberts

sig-signing-type breaks `named-checkconf -p` pretty output

Summary

When using the “sig-signing-type” keyword found inside a zone clause, it causes the named.conf file checker to silently exit with error code 1.

BIND version used

named v9.16.15

Steps to reproduce

The named.conf file simply has the following excerpt:

zone “public” {
   # . . .
   sig-signing-type 65243
   # . . .
};

Running

named-checkconf  -t .  -p  named.conf

will no longer output any content of the file.

What is the current bug behavior?

No longer outputs any file content

Exit code 1

What is the expected correct behavior?

Expected the original (but nicely rearranged) output of named.conf.

Relevant configuration files

Relevant logs and/or screenshots

No error output, no output output, just silent exit with an error code of 1.

Possible fixes

(If you can, link to the line of code that might be responsible for the problem.)

Assignee
Assign to
Time tracking