Comment 12 for bug 2012801

For the record, this is happening with 1:3.3.3-13184-g.3e9972c19-0ubuntu1~22.04.1 as well. So this is similar but not exact the same issue as https://bugs.launchpad.net/maas/+bug/2011841 in the end.

I'm going to collect information of this test deployment where 7 out of 25 LXD containers had two A/PRT records for one IP address.

$ juju run --all 'dig +short -x $(hostname -I)' | grep lxd-
    juju-38eb05-0-lxd-0.maas.
    juju-38eb05-0-lxd-2.maas.
    juju-38eb05-0-lxd-3.maas.
    juju-38eb05-0-lxd-4.maas.
    juju-38eb05-0-lxd-7.maas.
    juju-38eb05-1-lxd-6.maas.
    eth0.juju-38eb05-1-lxd-6.maas.
    juju-38eb05-2-lxd-2.maas.
    eth0.juju-38eb05-2-lxd-2.maas.
    juju-38eb05-0-lxd-1.maas.
    juju-38eb05-0-lxd-5.maas.
    juju-38eb05-0-lxd-6.maas.
    juju-38eb05-1-lxd-0.maas.
    juju-38eb05-1-lxd-1.maas.
    juju-38eb05-1-lxd-2.maas.
    juju-38eb05-1-lxd-3.maas.
    juju-38eb05-1-lxd-4.maas.
    eth0.juju-38eb05-1-lxd-4.maas.
    eth0.juju-38eb05-1-lxd-5.maas.
    juju-38eb05-1-lxd-5.maas.
    juju-38eb05-1-lxd-7.maas.
    eth0.juju-38eb05-1-lxd-7.maas.
    juju-38eb05-2-lxd-0.maas.
    juju-38eb05-2-lxd-1.maas.
    juju-38eb05-2-lxd-3.maas.
    juju-38eb05-2-lxd-4.maas.
    juju-38eb05-2-lxd-5.maas.
    eth0.juju-38eb05-2-lxd-5.maas.
    juju-38eb05-2-lxd-6.maas.
    juju-38eb05-2-lxd-7.maas.
    eth0.juju-38eb05-2-lxd-7.maas.
    juju-38eb05-2-lxd-8.