Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 530
    • Issues 530
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 101
    • Merge requests 101
  • 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
  • ISC Open Source Projects
  • BINDBIND
  • Issues
  • #298

Closed
Open
Created May 29, 2018 by Michał Kępień@michalOwner

Fix DNAME handling in DNSSEC tools

While reviewing !291 (merged), @marka noted that verifyzone()...

needs to check for DNAME records as these indicate bottom of zone like is_delegation() indicates bottom of zone. DNAME can appear at the zone apex and if is_delegation() returns true the DNAME test should not be made. zonecut needs to be set if the DNAME test is true so that check_no_nsec() is called for obscured records.

Edited Jun 06, 2018 by Michał Kępień
Assignee
Assign to
Time tracking