Blank DNS entry won't delete

We have found a DNS entry which causes a problem: It has no name value, so from MAAS the whole subdomain resolves to an unwanted IP, while from outside of MAAS it is already configured to resolve correctly. On the region controller:

maas:~$ head -12 /etc/bind/maas/zone.nimbus.pawsey.org.au 
; Zone file modified: 2022-10-27 19:11:26.026174.
$TTL 30
@   IN    SOA nimbus.pawsey.org.au. nobody.example.com. (
              0000986051 ; serial
              600 ; Refresh
              1800 ; Retry
              604800 ; Expire
              30 ; NXTTL
              )

@   30 IN NS pawsey.org.au.
 30 IN A 146.118.52.233

Notice the space starting the last line - by my reading that is why nimbus.pawsey.org.au resolves to that IP from MAAS. Externally it resolves correctly from upstream DNS to a different IP. At https:/…/MAAS/r/domain/1 (Name: nimbus.pawsey.org.au) I see what I think is the erroneous entry, screenshot attached of me trying to delete it.

maas SESSION dnsresources read | grep 146.118.52.233 finds the IP, but it is in an ‘ubuntu’ dnsresource record in another domain pawsey.org.au which also shows an entry in the web UI. That entry holds a lot of IPs, a few dozen named ‘ubuntu’. I think this is not relevant but am not sure.

$ maas SESSION dnsresource read 1899 | jq '.fqdn'
"ubuntu.pawsey.org.au"
$ maas SESSION dnsresource read 1899 | wc -l
117074
$ maas SESSION dnsresource read 1899 | jq '.ip_addresses | .[].ip' | wc -l
1511

I am left wondering if this snuck in quite some time ago (perhaps in an enlistment gone wrong?) in a previous version of MAAS, and in the current version that particular type of record can’t exist, and can’t be deleted. Do I need to dive into the database and delete something manually to fix this?

May I have some advice on this please?

I guess I just need to start digging around the database to see what I can find. That can be a job for next week.

sorry, @gregoryo2017 – we were on “sprint” last week in the team; i’ll make sure someone gets their head wrapped around this soonest.

Thanks - I tugged some other threads and am currently buried in automation, firewall and monitoring configs.

I’m still hoping for some attention on this. The problem still exists.

Hi @gregoryo2017,
To make sure I understand the intended setup and issue, you have a domain (DNS zone with regards to BIND) pawsey.org.au, and then you have a delegated zone of nimbus.pawsey.org.au, are either of these the default MAAS domain? And then in one of these , you have an ubuntu.pawset.org.au A record, but then the erroneous empty label record with the same IP?

Additionally, what is that IP tied to? Is it a machine within MAAS? If so, what is the status (i.e is it deployed?)?

I would recommend opening a bug report with these questions addressed there along with what MAAS version you are using, if you can.