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 565
    • Issues 565
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 93
    • Merge requests 93
  • 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
  • #795
Closed
Open
Issue created Dec 24, 2018 by Cathy Almond@cathyaDeveloper

rndc dumpdb output may be larger than expected - documentation update request

Ordinarily it should be anticipated by operators that dumping cache via rndc dumpdb is going to create a large file in the dump location. However there are some RRs whose presentation form can be significantly larger than their wire/memory format.

For example, the NSEC record format contains a bitmap which, when expanded can consume significantly more bytes.

This is a request for the ARM to be updated to warn operators that dumpdb output files can be significantly large - sometimes bigger than the operator would expect if there are many NSEC/NSEC3 RRsets currently cached.

Assignee
Assign to
Time tracking