Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • D deckard
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 34
    • Issues 34
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • 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
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Knot projects
  • deckard
  • Merge requests
  • !214

sets/resolver: another NSEC delegation to insecure zone

  • Review changes

  • Download
  • Email patches
  • Plain diff
Open Tomas Krizek requested to merge sets-delegation-to-insecure into master Oct 22, 2021
  • Overview 1
  • Commits 1
  • Pipelines 1
  • Changes 1

This reproduces the issue encounted in the wild by kresd, reported here: knot-resolver#679

The main point of the test is to have a delegation from secure to insecure subzone, when:

  • authoritative server for both zones is the same
  • the subzone is at least 2 labels below the parent zone apex
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: sets-delegation-to-insecure