> Then the NM update was pulled, and new installations aren't working at
all, even if we don't set the DNS config as described.
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
Also Till is
Do we have any idea when this will be fixed? Most of my users used to
get away with the DNS leakage and it was "only" a security problem but
stuff actually worked. Then the NM and other updates were shipped, we
set ipv4.dns-priority=-1 and ipv4.dns-search=~. and it all worked fine.
Then the NM
