48317bfc4b
On laptops and other devices which suspend frequently and are connected to WiFi, each suspension results in a loss of all cached DNS entries. This is problematic because some applications maintain their own DNS caches, which they also refresh immediately after suspensions. On WiFi networks that take some time to connect to, this results in applications getting a lot of non-authoritative NXDOMAIN responses in their caches, before systemd-resolved can get a connection to a real DNS server. This case should be prevented by the caching of stale data, but the blind flush of the cache prevents this. Further, the cache flushes disrupt statistics, and are unneeded to achieve the re-validation of DNSSEC responses. Nevertheless, maintain the flushing behavior on systems cases with no stale data retention, since it is possible that we are on an intranet with a local DNS server which was changed during suspension.
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack
Repositories with distribution packages built from git main are available on OBS