On Wednesday 2020-09-16 12:27, Matěj Cepl wrote:
Reading https://blog.oless.xyz/post/dnsfallback/ I got worried that when we adopt systemd-resolved as well, there we will be some better default than sending all your browsing metadata to the advertising agency. Couldn’t we at least make sure that yast generates some better defaults (DHCP leased DNS, etc.)?
The premise of the article is
"in case [...] the DHCP doesn’t provide the DNS"
and when that happens, yast can't help you either.
As for the default DNS list, a low-power resolver at opensuse.org might do the trick. Slow resolution would still be better than resolution by a big company - and it would give the user incentive to fix it, without making it overly difficult to access webpages for research..