We are very happy to release the third candidate of what will become dnsdist 1.8.0!
This release contains fixes for several issues that were found in the second release candidate.
- #12641: Use the correct source address when harvesting failed
- #12639: Fix a race when a cross-protocol query triggers an IO error
- #12638: Report the TCP latency for TCP-only Do53, DoT and DoH backends
- #12648: Report per-incoming transport latencies in the web interface
The first one is actually a follow-up to the “dnsdist is responding from the wrong source IP address in some setups” which was incompletely corrected in rc2. The second one is a race condition that might have been occurring in very specific cases of network errors during asynchronous processing of cross-protocol queries. The last issue is a bit more complicated: in 1.8.0 we decided to break down the latency metrics to provide a more accurate view of what was actually going on:
- global latency metrics are now per incoming protocol (Do53 UDP, Do53 TCP, DoT, DoH)
- backend latency metrics are split between UDP (Do53) and TCP (Do53 TCP, DoT, DoH)
This change brought some adjustment in the interfaces consuming these metrics, and it was reported that this was not quite right. The web interface, for example, was only reporting the UDP-based metrics and not the other ones.
We are immensely grateful to the PowerDNS community for the reporting of bugs, issues, feature requests, and especially to the submitters of fixes and implementations of features.