The DNS services does not support "colliding" networks.

Bug #1030848 reported by Raphaël Badin
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Low
Unassigned

Bug Description

If DNS is enabled, each nodegroup corresponds to a network with a forward DNS zone and a reverse DNS zone. The reverse DNS zone file is written, not for the network itself but for the corresponding enclosing classful network. I.e if one has a 192.168.2.1/22 network, the reverse zone file is written for the enclosing classful network: 192.168.2.1/24. This will obviously conflict if there is a "colliding" network (i.e. a network which has the same enclosing classful network), for instance 192.168.3.1/22.

In order to fix this, we need to implement RFC2317 (see http://www.indelible.org/ink/classless/ for an example).

Tags: dns
Revision history for this message
LaMont Jones (lamont) wrote :

See also bug #1356012, which looks to be a duplicate.

Revision history for this message
Andres Rodriguez (andreserl) wrote :

Hi!

We believe this is no longer an issue in the latest MAAS releases. As such, we are marking this bug report as invalid. If you believe this is still an issue, please re-open this bug report.

Thanks

Changed in maas:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.