[2.1, DNS, UI] Reverse DNS authority per subnet should be configurable in the UI

Bug #1634595 reported by Mike Pontillo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Mike Pontillo

Bug Description

It is not clear how to disable reverse DNS authority on a per-subnet basis. Currently, users are required to figure out the correct CLI/API incantation, and whether or not it is enabled is currently not visible enough (and thus would be difficult to for a customer to debug).

This option should be presented on the subnet details page in the UI.

Related: bug #1634294.

(This affects 2.0 as well, but I don't think it should be backported if we fix it in 2.1+.)

Tags: ux dns-ui docteam
Revision history for this message
Mike Pontillo (mpontillo) wrote :

Note: best case, this is a one-liner similar to the change to subnet-details.html in this branch:

https://code.launchpad.net/~mpontillo/maas/subnet-page-active-discovery-toggle/+merge/306917

tags: added: docteam
Changed in maas:
milestone: none → 2.4.x
summary: - [2.1] Reverse DNS authority per subnet should be configurable in the UI
+ [2.1, DNS, UI] Reverse DNS authority per subnet should be configurable
+ in the UI
tags: added: dns-ui
Revision history for this message
Mike Pontillo (mpontillo) wrote :

This feature the "Authoritative" toggle in the UI. We added the DNS UI for MAAS 2.4.0, so this is now fixed.

Changed in maas:
status: Triaged → Fix Committed
milestone: 2.4.x → 2.4.0beta2
assignee: nobody → Mike Pontillo (mpontillo)
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.