maas incorrectly overmanages DNS reverse zones
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
LaMont Jones | ||
1.9 |
Won't Fix
|
Wishlist
|
Unassigned | ||
maas (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
when I configure maas to manage DNS and DHCP for 10.89.64.0/20, it creates a reverse zone for 89.10.in-addr.arpa.
If 10.89.0.0/16 is in use for other things, and only 10.89.64.0/20 was delegated to scalingstack, then no reverse DNS can happen, since the parent zone will win the argument.
In this case, maas needs to create the following zones, and properly populate them (nsupdate will do the right thing if the zone declarations are correct):
64.
65.
...
78.
79.
(a total of 16 zones.)
Seen on trusty:
ii maas-dns 1.5.2+bzr2282-
Please let me know what other information you need.
lamont
Related branches
- Mike Pontillo (community): Approve
-
Diff: 917 lines (+389/-151)7 files modifiedetc/maas/templates/dns/named.conf.template (+4/-2)
src/maasserver/dns/config.py (+4/-3)
src/provisioningserver/dns/actions.py (+17/-12)
src/provisioningserver/dns/config.py (+15/-4)
src/provisioningserver/dns/tests/test_actions.py (+4/-4)
src/provisioningserver/dns/tests/test_zoneconfig.py (+179/-52)
src/provisioningserver/dns/zoneconfig.py (+166/-74)
- MAAS Committers: Pending requested
-
Diff: 917 lines (+389/-151)7 files modifiedetc/maas/templates/dns/named.conf.template (+4/-2)
src/maasserver/dns/config.py (+4/-3)
src/provisioningserver/dns/actions.py (+17/-12)
src/provisioningserver/dns/config.py (+15/-4)
src/provisioningserver/dns/tests/test_actions.py (+4/-4)
src/provisioningserver/dns/tests/test_zoneconfig.py (+179/-52)
src/provisioningserver/dns/zoneconfig.py (+166/-74)
- Blake Rouse (community): Approve
-
Diff: 27 lines (+8/-2)1 file modifiedsrc/maastesting/factory.py (+8/-2)
- Blake Rouse (community): Approve
-
Diff: 661 lines (+238/-26)14 files modifiedsrc/maasserver/api/subnets.py (+10/-1)
src/maasserver/api/tests/test_subnets.py (+7/-0)
src/maasserver/dns/tests/test_config.py (+12/-6)
src/maasserver/dns/tests/test_zonegenerator.py (+53/-9)
src/maasserver/dns/zonegenerator.py (+38/-2)
src/maasserver/enum.py (+26/-0)
src/maasserver/forms_subnet.py (+5/-0)
src/maasserver/migrations/builtin/maasserver/0023_add_rdns_mode.py (+22/-0)
src/maasserver/models/subnet.py (+7/-0)
src/maasserver/models/tests/test_subnet.py (+5/-2)
src/maasserver/testing/factory.py (+3/-2)
src/maasserver/websockets/handlers/tests/test_subnet.py (+1/-0)
src/provisioningserver/dns/tests/test_zoneconfig.py (+4/-2)
src/provisioningserver/dns/zoneconfig.py (+45/-2)
summary: |
- maas incorrectly overmanages DNS + maas incorrectly overmanages DNS reverse zones |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Status changed to 'Confirmed' because the bug affects multiple users.