On Fri, Mar 24, 2023 at 7:41 AM Lennart Poettering
wrote:
>
>
> There are conflicting goals here: nice, reliably behaviour that config
> changes are guaranteed to be taken into account, and a simple goal of
> performance to reduce these stat calls.
>
An option to simply ignore resolv.conf
I think it is fairly easy. If the /etc/resolv.conf changes not by a
change of systemd-resolved, it is very likely the address specified in
it does not point to resolved anymore. In that sense it does not matter
what systemd-resolved does with such information and how quickly.
Does it update
On Fr, 24.03.23 03:16, Petr Menšík (pemen...@redhat.com) wrote:
> Even if it could not use filesystem monitoring, I guess it could check those
> files only once per second or so. Should not depend on number of done
> queries.
It's not so easy. We generally want to give the guarantee that if
Hi Robert,
interesting. It seems resolved is not expecting so heavy usage. Consider
other cache until this is fixed, unbound or dnsmasq might be a good choice.
Please create an issue for it on https://github.com/systemd/systemd.
Especially when it can use the fact it is a deamon, it should
Hello, I'm using systemd-resolved on the server which performs a lot
of DNS queries (~20K per second) and systemd-resolved helps a lot
providing a cache:
Cache
Current Cache Size: 263
Cache Hits: 30928976
Cache Misses: 2961
However, systemd-resolved process almost
