designate-bind needs extra binding support

Bug #1783678 reported by Nobuto Murata on 2018-07-26
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Designate-Bind Charm
Nobuto Murata

Bug Description

designate-bind currently has dns-backend:bind-rndc relation so we can specify which network to accept rndc command from designate control plane. designate-bind is to be exposed for clients outside of a Juju model for actual name resolution, but we don't have a way to add an extra network to accept dns queries.

Would be nice to have an extra binding support in the charm.

Nobuto Murata (nobuto) on 2018-07-26
Changed in charm-designate-bind:
assignee: nobody → Nobuto Murata (nobuto)

Fix proposed to branch: master

Changed in charm-designate-bind:
status: New → In Progress

Submitter: Zuul
Branch: master

commit af9f3e79b560776ba3640d987dffb173c9504b5c
Author: Nobuto Murata <email address hidden>
Date: Thu Jul 26 13:23:55 2018 +0900

    Add dns-frontend extra binding

    Another network space can be added to offer DNS service to clients
    outside of the Juju model.

    Change-Id: Ida1dd81bc4e2a2f1778ffa5d747a88c860164def
    Closes-Bug: #1783678

Changed in charm-designate-bind:
status: In Progress → Fix Committed
David Ames (thedac) on 2018-09-06
Changed in charm-designate-bind:
milestone: none → 18.08
James Page (james-page) on 2018-09-12
Changed in charm-designate-bind:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers