Ronan Pigott
27eedfa0ef
sd-resolved does dnssec "backwards" compared to most resolvers. A typical strategy is to start from the DNS root and gather the requisite keys on the way down, but sd-resolved requests the final answer it wants and then goes searching for the requisite keys later. We don't know in advance under which names we should expect to find those keys, because we don't know the zone cuts a priori, but we can use what we have found in prior responses to make an educated guess. This was more or less the intent of47690634f1, but it was partially regressed ind840783db5while fixing a bug handling totally empty responses. Fixes #37472 Ref:47690634f1("resolved: don't request the SOA for every dns label") Fixes:d840783db5("resolved: always progress DS queries")
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, and also repositories with packages built from the latest stable release