Comment 5 for bug 1776604

I have a customer using 2.3 who needs to update the DNS record for their machine to be the correct (primary) interface in this scenario. Unfortunately in 2.3 it seems you cannot update the existing DNS record like you can in 2.4 (maas dnsresources read does not return any of the machine hostname records, thus you can't update them - and if you create a record alongside it - DNS returns both IPs instead of replacing the auto generated record)

Is there some other way we can work around this issue on 2.3? As the customer is on Xenial, it seems 2.4 is not available for Xenial so it is not feasible to upgrade to 2.4 for them. Thus we need a fix or workaround for 2.3.