Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
BIND
BIND
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 627
    • Issues 627
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 116
    • Merge Requests 116
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • BINDBIND
  • Issues
  • #503

Closed
Open
Created Aug 27, 2018 by Evan Hunt@eachOwner

dnsrps test no longer runs

The DNSRPS portions of the rpz and rpzrecurse tests were inadvertently disabled some time ago. It doesn't cause a test failure; the only way to know it happened is that "DNSRPS is disabled" appears in the test output. We do have a jenkins system that builds with --enable-dnsrps, but because the test itself thought DNSRPS had been disabled, it was skipped over and nobody was the wiser.

The culprit seems to have been commit b98a9207.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None