Updating DNS records yields unexpected results

[Alberto Donato]

When editing records on the Domain details page unexpected results can happen.

See the following cases:

1) create a record as "foo A 1.1.1.1"
2) remove the record.
3) a new special record appears as "1-1-1-1 A 1.1.1.1" which can't be edited/deleted from the UI (the staticipaddress can be removed via API)
4) create an A record with the same IP
5) the special record disappears

similar case:

1) create a record as "foo A 1.1.1.1"
2) update the record with the IP "2.2.2.2"
3) a special record appears as "1-1-1-1 A 1.1.1.1"
4) edit the record again with the original IP "1.1.1.1"
5) now there's a special record as "2-2-2-2 A 2.2.2.2"

it seems in both cases we should delete the original IP (or update the value in the latter case)

Another (possibly more broken) case is this:

1) create a record as "foo A 1.1.1.1"
2) create a record as "foo A 2.2.2.2"
3) change the name for the first record to "bar"
4) a special record appears as "2-2-2-2 A 2.2.2.2"

I this case we should either rename all "foo" records, or leave the second one intact.

[Caleb Ellis (caleb-ellis)]

I think this might be an issue with the websocket api, specifically the "domain.update_address_record" and "domain.delete_address_record" methods.

I'm in the process of rebuilding the DNS section in React and I'm coming across the same issue whenever I delete or update an address record. Other record types seem to be fine which I believe is because they use the "domain.update_dnsdata" and "domain.delete_dnsdata" methods instead.

Not sure if you are able to confirm it's an api issue, or maybe explain how the existing methods are supposed to be used?

[Caleb Ellis (caleb-ellis)]

This also seems to be the case when using the "domain.update_dnsresource" and "domain.delete_dnsresource" methods. At a bit of a loss with this one.

[Jerzy Husakowski (jhusakowski)]

See mail from 25th June 2021 to the MAAS Design list.

[Thorsten Merten (thorsten-merten)]

Need to check if this is maas-ui only of something in the websocket/backend