Comment 5 for bug 1896772

On Thu, Sep 24, 2020 at 09:42:28PM -0000, Balint Reczey wrote:
> The latest upload (246.6-1ubuntu1) may have fixed this as well.

This happened again just now when I upgraded my system to the new
systemd, so I assume not.

Here's a log snippet of restarting:

Sep 29 09:28:14 surprise systemd[1]: Starting Network Name Resolution...
Sep 29 09:28:15 surprise systemd-resolved[31479]: Positive Trust Anchors:
Sep 29 09:28:15 surprise systemd-resolved[31479]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Sep 29 09:28:15 surprise systemd-resolved[31479]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test
Sep 29 09:28:15 surprise systemd-resolved[31479]: Using system hostname 'surprise'.
Sep 29 09:28:15 surprise systemd[1]: Started Network Name Resolution.

At this point, I do not have working DNS resolution. If I reconnect my
network interface, then I do get it, but I see this line in the log,
repeated multiple times:

Sep 29 09:28:23 surprise systemd-resolved[31479]: Failed to save link data /run/systemd/resolve/netif/2: Permission denied

/run/systemd/resolve is owned by systemd-resolve, but
/run/systemd/resolve/netif is owned by root.

Could this be related to the issue I'm observing?