Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Knot DNS Knot DNS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 24
    • Issues 24
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 10
    • Merge requests 10
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Knot projects
  • Knot DNSKnot DNS
  • Merge requests
  • !1135

Open
Created May 06, 2020 by Libor Peltan@lpeltanMaintainer
  • Report abuse
Report abuse

Nsec dname cmp zero

  • Overview 1
  • Commits 2
  • Pipelines 1
  • Changes 9

This "solves" the situation when records in zone are wrongly ordered because of knot_dname_lf with connection to \000.

The user is warned when creating NSEC tree, when owner with \000 is present.

NSEC tree creation/update fails, if this directly affects zone ordering.

This does not solve many situations when there is collision of names after knot_dname_lf applied!

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: nsec_dname_cmp_zero