cp -a is supposed to preserve ownership. -a means "-dR --preserve=all".
Could someone look at what happens, by displaying more than just the /run/systemd/resolve/stub-resolv.conf file? All files in /run/systemd/resolve/ are relevant here.
This has more smells of being affected my UMASK and probably other settings, otherwise it wouldn't be a perm 600 file.
Nevertheless, running 0000usepeerdns is wrong in all cases, especially with NetworkManager. That file probably should go; replaced by something that will use systemd-resolved's interfaces instead if they are available, and definitely never runs when NetworkManager is running.
cp -a is supposed to preserve ownership. -a means "-dR --preserve=all".
Could someone look at what happens, by displaying more than just the /run/systemd/ resolve/ stub-resolv. conf file? All files in /run/systemd/ resolve/ are relevant here.
This has more smells of being affected my UMASK and probably other settings, otherwise it wouldn't be a perm 600 file.
Nevertheless, running 0000usepeerdns is wrong in all cases, especially with NetworkManager. That file probably should go; replaced by something that will use systemd-resolved's interfaces instead if they are available, and definitely never runs when NetworkManager is running.