[2.x] User gets no control over @ RRset in DNS domains

Bug #1672220 reported by LaMont Jones on 2017-03-12
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
High
LaMont Jones

Bug Description

It makes sense that the @ A, AAAA, & NS RRsets include the region controller, in addition to anything explicitly added by the admin (via dnsresources and dnsresource-records).

However, other domains should be completely under the control of the admin, and should include the region controller's "default-zone name" in the NS RRset, and not populate any address RRset in the domain, so that the admin has full control over the domain. (Nothing says that the top of a domain needs to be the region controller, other than our buggy thinking when we added multiple domains.)

Related branches

Changed in maas:
milestone: none → 2.2.0
Changed in maas:
milestone: 2.2.0 → 2.2.0rc2
Changed in maas:
importance: Undecided → High
LaMont Jones (lamont) on 2017-04-05
Changed in maas:
assignee: nobody → LaMont Jones (lamont)
status: New → In Progress
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
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