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 526
    • Issues 526
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 102
    • Merge requests 102
  • 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
  • #1744

Closed
Open
Created Apr 07, 2020 by lac-0073@lac-0073

ttl suddenly jumped into a big value

my version: BIND 9.11.4

local Cache ttl is 8, but dig value far beyond ttl

image

I have Captured, you can check the lines 50&51 104&106 of the followongh file

dns_ttl.pcap

53.1.42.13 tell 53.1.82.19 cluster01.myobs.com ttl 5 image

but 53.1.82.19 tell 53.1.42.16 cluster01.myobs.com ttl 1585212656 image

and use "dig cluster001.myobs.com" query also return 15821216xx image

and use "rndc dumpdb" generate cache_dump.db, can not find "cluster001.myobs.com" image

I can't understand how such a big ttl came

Edited Apr 07, 2020 by lac-0073
Assignee
Assign to
Time tracking