[2.4, DNS, UI] Multiple address records should be represented as a single record

Bug #1761804 reported by Mike Pontillo on 2018-04-06
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Low
Unassigned

Bug Description

In MAAS, we model each DNS record associated with an address as a single DNS resource in the database linked to multiple StaticIPAddress records. These become A or AAAA records when rendered in the DNS zone.

The UI currently behaves as if each A or AAAA record is a separate entity. While this is generally OK, it does have the strange side effect that changing the TTL for a single address record would unexpectedly change all of them.

If we display multiple address records, we will have to think about how to represent DNS resources that have a combination of A, AAAA, and other record types (such as MX or TXT).

Changed in maas:
milestone: next → 2.4.x
tags: added: dns-ui
summary: - [2.4, UI] Multiple address records should be represented as a single
- record
+ [2.4, DNS, UI] Multiple address records should be represented as a
+ single record
LaMont Jones (lamont) wrote :

Part of the issue here is that they really are several individual A (or AAAA) records, with the imposed constraint that the TTL for all RRs of a given type MUST be identical. When you add in that several of the RRs are added dynamically as the node is deployed, it gets even more interesting.

Perhaps just a warning when the user goes to edit the TTL telling him that it will change all of that RRtype? (A an AAAA can have different TTLs, of course.)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers