Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 603
    • Issues 603
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 87
    • Merge requests 87
  • 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
  • #101
Closed
Open
Issue created Feb 23, 2018 by Vicky Risk@vickyDeveloper

[Support#12071] [RT#46548] Output stale/expired data with 'rndc dumpdb'

Now that there are ways to serve stale data from the cache, it would be good to be able to see with dumpdb what records there are that might end up being served, even though those records wouldn't show up in a regular dumpdb.

Update 2018-12-13: Stale data is actually already included in the dumpdb output. In addition to the stale RRsets it would be nice to also output for how long this stale data is still available in the cache. This needs to be determined by the configuration option 'serve-stale-max-ttl'.

Edited Jan 24, 2019 by Matthijs Mekking
Assignee
Assign to
Time tracking