Skip to content
GitLab
Projects Groups Topics 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
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 634
    • Issues 634
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 90
    • Merge requests 90
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • 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
  • #3603
Closed
Open
Issue created Oct 13, 2022 by Arаm Sаrgsyаn@aramDeveloper

Resolver prefetch eligibility edge case bug

According to ARM, the prefetch "eligibility" parameter is the smallest original TTL value that is accepted for a record to be eligible for prefetching, but in fact, when the original TTL value is equal to the eligibility value, the record is not treated as eligible for prefetching.

For example, with prefetch 4 10; configuration in tests/system/resolver/ns5 instance, prefetch doesn't work for the following records in tests/system/resolver/ns4:

fetchall  10              TXT     A short ttl
fetchall  10              A     1.2.3.4
fetchall  10              AAAA    ::1

Although the test passes because it fails to check that prefetch occurred.

Edited Oct 13, 2022 by Arаm Sаrgsyаn
Assignee
Assign to
Time tracking