So I've looked at this and I think it needs to be a won't-fix as it stands, but I want your opinion first because there's something else MAAS should be doing.
LXCs have never been supported as a first class citizen in MAAS, so the fact that a non-MAAS node obtained an IP with a DNS entry is a little bit of a side effect of how it was previously implemented. The DNS entries from dynamically assigned DHCP IPs are dangerous because they can go out of date at any time and MAAS has no way to track that in a timely fashion, and in fact this is exactly what was happening in OIL which pushed us to doing the static IP solution. MAAS has an API to request an IP address separately to whatever the nodes may get assigned. It was intended that juju-created LXCs use this API to get an IP and configure the LXC network interface(s) appropriately. What's missing from MAAS's API is that the IPs obtained on the API don't have the option of being given a DNS entry. If we fix that, and then juju starts using the API, everything will be working perfectly. Let me know what you think. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382190 Title: LXCs assigned IPs by MAAS DHCP lack DNS PTR entries To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1382190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
