Comment 4 for bug 1473069

Actually, that is wrong.
The container addresses already have a PTR and A record in the MAAS DNS nameserver, so we are back to a juju problem with ordering of the addresses.
But it seems to be based on the fact that the hostname returned by MAAS DNS is being ignored by Juju and it is selecting by IP address instead of selecting the hostname.

So, in /etc/bind9/maas/zone.hv.dazcloud.com:
$GENERATE 51-99 192-168-92-$ IN A 192.168.92.$

& in /etc/bind9/maas/zone.92.168.192.in-addr.arpa:
$GENERATE 51-99 $.92.168.192.in-addr.arpa. IN PTR 192-168-92-$.hv.dazcloud.com.

Testing this from a juju machine, the hostname lookup works as expected, but juju status still returns a different IP address as both the private and public address and no hostname.