Public bug reported:
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.89.10.in-addr.arpa
65.89.10.in-addr.arpa
...
78.89.10.in-addr.arpa
79.89.10.in-addr.arpa
(a total of 16 zones.)
Seen on trusty:
ii maas-dns 1.5.2+bzr2282-0ubuntu0.2 all MAAS DNS server
Please let me know what other information you need.
lamont
** Affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- maas incorrectly overmanages DNS
+ maas incorrectly overmanages DNS reverse zones
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1356012
Title:
maas incorrectly overmanages DNS reverse zones
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1356012/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
