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 576
    • Issues 576
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 113
    • Merge requests 113
  • 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
  • #1586
Closed
Open
Issue created Jan 24, 2020 by Vicky Risk@vickyDeveloper0 of 3 checklist items completed0/3 checklist items

BIND hook module for dynamically-created reverse PTR records for IPv4, IPv6 [ISC-support #15935]

We have had requests in the past for some mechanism for creating reverse PTR records on the fly for IPv6 addresses. The reason for needing to create these dynamically is, of course, the address space is so vast, it is just unfeasible or at least inefficient to create PTR records in advance for all possible needs.

This is a somewhat controversial feature, because a lot of ppl now think that reverse PTR records are unnecessary, so it is an example of a feature some users might think would be more clutter and unnecessary code risk in BIND. Therefore, can we consider using the new BIND Hooks interface to create an optional module for dynamic creation of reverse PTR records?

  • Ideally this would only come into play after checking for the presence of an actual reverse PRT record, and then create on on the fly if there isn't one.
  • It would be ideal if it is possible to also sign this record on the fly, but the feature will still be usable to many people even if it is not possible to sign it.
  • There is no real reason to restrict this to IPv6 addresses. We may as well also support IPv4 addresses too, particularly if we will only synthesize a record if there is none already configured.

We do have an existing support customer request for this.

Edited Jan 29, 2020 by Cathy Almond
Assignee
Assign to
Time tracking