Comment 61 for bug 1754671

> That's weird, do you understand why? The update was deleted so you should be back to initial
> situation, we had no change to the previous package build

Other package changes? Certainly systemd-resolver although we don't use that (because of a previous VPN DNS leak problem) we use dnsmasq.

My original thought was that it was the VPN config change that we'd made to cope with the new NM, but testing seems to show it isn't that.

Now we have a failure mode which some people had *occasionally* reported before, where even VPN lookups which *must* go to the VPN, for the company domain, are not. This was just occasional before; now it seems to happen all the time. I haven't done a thorough investigation since just putting the updated NM back has been enough to fix it.