Skip to content
GitLab
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 568
    • Issues 568
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 100
    • Merge requests 100
  • 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
  • #950
Closed
Open
Issue created Mar 20, 2019 by Michał Kępień@michalOwner

System tests send out DNS queries to non-local IP addresses

Some named instances used in system tests send outbound queries to non-local IP addresses. This should not happen as test traffic should be confined to the host running the tests.

This issue was severely aggravated by !145 (merged), which changed the default value for the dnssec-validation setting to auto. Since this change also applies to servers configured with recursion no;, a lot more named instances used during system tests started sending ./NS and ./DNSKEY queries over non-standard ports towards real root servers. (See also #949.)

Assignee
Assign to
Time tracking