$ dig +short @MAAS_DNS juju-b1c448-0-lxd-0.maas
-> no record
HOSTNAME.maas as in juju-b1c448-0-lxd-0.maas is expected as FQDN in many places like charms' code, fixing a regression of having duplicate records is good, but losing the resolution of the "canonical" FQDN may be a bigger problem.
> 2. probably without eth0 is preferred to be the "canonical" hostname of the device
Just to add to this, missing HOSTNAME.maas response is a problem to many areas.
$ dig +short @MAAS_DNS eth0.juju- b1c448- 0-lxd-0. maas
192.168.151.199
$ dig +short @MAAS_DNS juju-b1c448- 0-lxd-0. maas
-> no record
HOSTNAME.maas as in juju-b1c448- 0-lxd-0. maas is expected as FQDN in many places like charms' code, fixing a regression of having duplicate records is good, but losing the resolution of the "canonical" FQDN may be a bigger problem.