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 524
    • Issues 524
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 105
    • Merge requests 105
  • 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
  • #1812

Closed
Open
Created May 05, 2020 by Peter Davies@peterdDeveloper

Unexpected output from named-checkconf

Unexpected output from named-checkconf: When run "named-checkconf -p " appends extra test to server lines in static-stub zones input: zone "10.in-addr.arpa" { type static-stub; server-addresses { 199.81.216.126; 204.135.12.254; }; };

expected output: zone "10.in-addr.arpa" { type static-stub; server-addresses { 199.81.216.126; 204.135.12.254; }; }; received output: zone "10.in-addr.arpa" { type static-stub; server-addresses { 199.81.216.126 dscp 4294950590; 204.135.12.254 dscp 4294950590; };

This behaviour appears to start at release 9.11.6

see RT #16328

Assignee
Assign to
Time tracking