Lennart Poettering
Lennart Poettering
> This doesn't seem to work for me. I specifically defined quad9 as a Fallback DNS, but I was sure it had to do something else since it never resolved...
i am not really convinced either. We shouldn't add additional options like this just for ordering.
> Another usecase for this I just thought up: the instance of repart that runs at boot can use this to decide whether or not to create a /home partition....
sounds generally fine to me, just nitpicks.
lgtm, but please rebase and fix that () thing.
Yeah, you have one level of AND and one of OR exposed in journalctl. (internally there are more levels). NOT is currently not supported, but there's already an item for...
no updates. nobody worked on this so far. situation has not changed. Somebody needs to sit down and do the work.
Uh. the idea of resolved was that every tool that owns a netif can set its config on that, and doesn't end up fighting for the global dns server. Hence,...
I don't get it. A global DNS server config is always just weird. Needs to be per-interface. Whener DoT, or DoH or classic DNS is used is just a choice...
What I'd be fine with, if we'd have an API to allow explicit allocation of additional resolved "scopes", that basically package a set of dns server addresses and routing domains...