Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 569
    • Issues 569
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 112
    • Merge requests 112
  • 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
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • BINDBIND
  • Issues
  • #1592
Closed
Open
Issue created Jan 30, 2020 by Evan Hunt@eachOwner

catalog zones fail if a zone name contains a slash

Francisco Obispo at Uniregistry reported that a catalog zone was failing with:

Jan 22 12:19:40 ns2 named[7408]: catz: error "unexpected token" while trying to generate config for zone "0/27.145.96.64.in-addr.arpa"

This is likely due to the zone name containing a slash, which can't be used when it's expanded into a filename.

There's already code in catz.c to substitute a hash when the zone name is too long; it needs to also do so when an illegal character is found in the zone name.

Assignee
Assign to
Time tracking