MAAS - multiple DNS zones with the same duplicated zone name
Bug #1597266 reported by
Lorenzo Cavassa
This bug report is a duplicate of:
Bug #1356012: maas incorrectly overmanages DNS reverse zones.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
New
|
Undecided
|
Unassigned |
Bug Description
Hi,
Running MAAS 1.9.3
I have 2 different subnets, 10.237.44.128/25 and 10.237.44.64/26, defined as MAAS managed networks.
MAAS generates an /etc/bind/
https:/
and then bind fails to start because there are multiple zones using the same zone name:
44.237.
and the same zone file:
/etc/bind/
This is an excerpt from the /var/log/syslog file:
To post a comment you must log in.
With maas 2.0, you will have the option of creating the 44.237. 10.in-addr. arpa zone (delegating to the two other zones -- default), or simply creating the rfc2317 zones, and relying on your existing 44.237. 10.in-addr. arpa authoritative nameserver for the delegation to MAAS.