Skip to content

GitLab

  • Menu
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 523
    • Issues 523
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 94
    • Merge requests 94
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & 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 Projects
  • BINDBIND
  • Issues
  • #389
Closed
Open
Created Jul 07, 2018 by Evan Hunt@eachOwner

cache dump lists stale TTLs - intentional?

While backporting serve-stale to the 9.11 subscription branch I noticed that rndc dumpdb -cache has changed its output; records in the cache dump now show their total time to live, not just the time until they become stale.

The dump file does include a line that indicates what the stale TTL is set to. You can subtract that from the reported TTL and find out what the record's original TTL was in the auth server reply. So this may be fine, but it wasn't the behavior I was expecting and I wonder if it needs more condsideration.

Assignee
Assign to
Time tracking