Thanks for your continued help in testing the Pi-hole beta and the dnsmasq
release candidate.
Only recently, we were able to discover an issue with incorrectly handled replies when dnsmasq
wasn't able to cache them. This finally lead to a series of three patches sent upstream to the dnsmasq
project so everyone, also outside of Pi-hole, will be able to benefit from this involved testing. Working on the patches, Simon Kelley, the maintainer of dnsmasq
found yet another long-standing bug with CNAME
chains ending in a PTR
record not being handled correctly. This lead to the second release candidate of the new dnsmasq
being tagged.
Our great community is really something we can be proud of. And it pleases me to be part of it.
Further changes to the beta since we originally wrote the release notes you've seen above:
- Fix
dnsmasq
server
option interpretation (fix sent and accepted upstream) - Allow users to configure how FTL reacts to queries when the gravity database is not available (
REPLY_WHEN_BUSY
option) - Rate-limiting events are shown in the Pi-hole diagnosis system so you get notified on the web dashboard if any of your clients is rate-limited
- Also display DNSSEC status of cache replies and internally generated DNSSEC-related queries