[2.x] User gets no control over @ RRset in DNS domains
Bug #1672220 reported by
LaMont Jones
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
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-
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
lp:~lamont/maas/bug-1672220
- Mike Pontillo (community): Approve
-
Diff: 697 lines (+180/-92)7 files modifiedsrc/maasserver/dns/tests/test_zonegenerator.py (+65/-2)
src/maasserver/dns/zonegenerator.py (+30/-11)
src/maasserver/models/domain.py (+16/-9)
src/maasserver/models/tests/test_domain.py (+37/-14)
src/provisioningserver/dns/tests/test_zoneconfig.py (+20/-37)
src/provisioningserver/dns/zoneconfig.py (+11/-18)
src/provisioningserver/templates/dns/zone.template (+1/-1)
| Changed in maas: | |
| milestone: | none → 2.2.0 |
| Changed in maas: | |
| milestone: | 2.2.0 → 2.2.0rc2 |
| Changed in maas: | |
| importance: | Undecided → High |
| 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.
