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 528
    • Issues 528
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 95
    • Merge requests 95
  • 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
  • #893
Closed
Open
Created Feb 21, 2019 by Michał Kępień@michalOwner

Options set in /etc/resolv.conf affect dig behavior during system tests

In BIND 9.11, where liblwres is used for parsing /etc/resolv.conf, certain options directives affect dig's default settings. Namely, timeout and attempts override the defaults for +timeout (5 seconds) and +tries (3). Depending on the values of the options set in /etc/resolv.conf, system tests assuming dig's default settings are in effect may fail.

I do not think this is a bug in dig. At any rate, changing the aforementioned behavior in BIND 9.11 would mean introducing a functional change in an ESV release.

BIND 9.12+ uses libirs instead of liblwres for parsing /etc/resolv.conf. Since libirs does not process the aforementioned options directives, BIND 9.12+ is not affected by this issue.

Assignee
Assign to
Time tracking