Comment 6 for bug 1896772

I've just tested: changing the ownership of /run/systemd/resolve/netif to systemd-resolve:systemd-resolve resolves (haha) this issue. The first restart of systemd-resolved after the change did not address it (because the permissions issue means that the state was not persisted); on a network interface reconnect, the state _is_ persisted, so future systemd-resolved restarts do not lose DNS resolution.