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 111
    • Merge requests 111
  • 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
  • #693
Closed
Open
Issue created Nov 14, 2018 by Mark Andrews@markaOwner

Automatically configure DNS64 when forwarding is enabled for IPV4ONLY.ARPA

When the IPV4ONLY.ARPA namespace is covered by a forward directive periodically query for IPV4ONLY.ARPA/AAAA using that forward directive and if AAAA records are found, construct DNS64 prefixes based on the returned addresses. See RFC 7050.

Additionally look for IPV4ONLY.ARPA/APL for exclusion acls. Family 1 for mapped and family 2 for excluded. If not found populate mapped with RFC 1918 addresses and populate excluded with ::ffff:0:0/96 as per RFC 6174.

Assignee
Assign to
Time tracking