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 532
    • Issues 532
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 100
    • Merge requests 100
  • 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
  • #661

Closed
Open
Created Nov 06, 2018 by Petr Špaček@pspacekOwner

rich configuration API

Description

BIND is hard to configure from outside using APIs, especially when it comes to reading configuration back. It is of course possible to always generate full config file from scratch and restart named process but it has some drawbacks:

  • previous configuration which requires modification must be stored elsewhere (because named.conf is hard to parse from outside)
  • it makes combining manual tweaking in config with automation becomes harder than necessary

Request

In general I suggest to provide an configuration API which allows user to tweak running instance, and very importantly, also obtain configuration from the running instance. It would make life much easier for people who want to manage BIND using external tools.

Links / references

Assignee
Assign to
Time tracking