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 526
    • Issues 526
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 102
    • Merge requests 102
  • 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
  • #1539

Closed
Open
Created Jan 03, 2020 by David M Walker@datamgmt

Code edits required to support a new class.

Description

When adding a new class - a rare occurance but one I encountered - you are required to add a new case statement to the function dns_rdataclass_fromtext in lib/dns/rcode.c of the form

case 'e':
    COMPARE("exclass", dns_rdataclass_exclass);
    break;

This is un-documented, limited to 26 characters of which 5 are already taken and prohibits generic builds in line with the design objectives on BIND9

However I do not the comment at the start of the code

/*
 * This uses lots of hard coded values, but how often do we actually
 * add classes?
 */

Request

A generic solution that does not require the code to be edited when generating a new build.

Links / references

Assignee
Assign to
Time tracking