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 567
    • Issues 567
    • 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
  • #660
Closed
Open
Issue created Nov 06, 2018 by Petr Špaček@pspacekOwner

rndc showzone does not work for all zones

Summary

It seems that command rndc showzone does not work for certain zones, at very least for built-in zones. This is super inconvenient for scripts which iterate over all zones with intent to get and modify configuration of running process.

BIND version used

BIND 9.13.0-dev id:883a9485e9 commit 883a9485 Date: Thu Feb 15 11:56:13 2018 -0800

Steps to reproduce

$ rndc showzone 10.in-addr.arpa.

What is the current bug behavior?

rndc: 'showzone' failed: failure

What is the expected correct behavior?

Ideally equivalent which can be copied into back to config file and does not break anything. (Alternatively a more useful error message.)

Edited Nov 06, 2018 by Petr Špaček
Assignee
Assign to
Time tracking