Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
BIND
BIND
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 389
    • Issues 389
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 68
    • Merge Requests 68
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Packages
    • Packages
    • Container Registry
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ISC Open Source Projects
  • BINDBIND
  • Issues
  • #749

Closed
Open
Opened Nov 28, 2018 by Cathy Almond@cathya
  • Report abuse
  • New issue
Report abuse New issue

Some NSEC3 names are (unexpectedly) lower case

As observed while troubleshooting a support issue, although it causes no validation problems (names are case-insensitive) we were surprised to encounter NSEC3 hash names that were all lower case in the zone.

BIND was the only signer, and all other NSEC3 hash names were upper case.

Is there a corner case scenario in which the lower-cased names are used when creating an NSEC3 RR?

https://support.isc.org/Ticket/Display.html?id=13752

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
2
Labels
Bug Customer
Assign labels
  • View project labels
Reference: isc-projects/bind9#749