Comment 4 for bug 2007192

Hello Anton,
Thank you for the response. Firstly, I would be content to update the database directly but it would be easier if I knew how to follow some of the foreign keys. That is, maasserver_dnsresource table has no identifying information in it, and oddly enough it only has 41 rows as compared to over 400 machines controlled by MAAS.

Previously I was looking at the name 'ubuntu', so just looking at that, the entry is
 1899 | 2020-03-23 14:34:54.656713+08 | 2020-03-23 14:34:54.656713+08 | ubuntu | 0 |
(Oh hang on, ID 1899 matches, but I am still not sure how accurate that is.)

However, I am now seeing new behaviour. From both rackd and regiond servers:

$ dig nimbus.pawsey.org.au +short
146.118.53.173
146.118.52.233

and sure enough:

$ head -13 /etc/bind/maas/zone.nimbus.pawsey.org.au | tail -3
@ 30 IN NS pawsey.org.au.
 30 IN A 146.118.53.173
 30 IN A 146.118.52.233

146.118.53.173 was marked as Discovered on a baremetal node in Ready state which I have been working with today. I have just deployed it, and it has been autoassigned a different IP in that subnet, but the DNS entry remains.
146.118.52.233 is marked as Discovered on a baremetal node which has for many months been deployed as a MAAS KVM Pod host, although it too has a different autoassigned IP in that subnet.

What should I do now?