Released February 12th, 2015.
This version contains a mix of speedups and improvements, the combined effect of which is vastly improved resilience against traffic spikes and malicious query overloads.
Of further note is the massive community contribution, mostly over Christmas. Especially Ruben Kerkhof, Pieter Lexis, Kees Monshouwer and Aki Tuomi delivered a lot of love. Thanks!
- Removal of dead code here and there 04dc6d618
- Per-qtype response counters are now 64 bit 297bb6acf on 64 bit systems
- Add IPv6 addresses for b and c.root-servers.net hints efc259542
- Add IP address to logging about terminated queries 37aa9904d
- Improve qtype name logging fab3ed345 (Aki Tuomi)
- Redefine ‘BAD_NETS’ for dont-query based on newer IANA guidance 12cd44ee0 (lochiiconnectivity)
- Add documentation links to systemd unit eb154adfd (Ruben Kerkhof)
- Upgrade embedded PolarSSL to 1.3.9: d330a2ea1
- yahttp upgrade c29097577 c65a57e88 (Aki Tuomi)
- Replace . in hostnames by – for Carbon so as not to confuse Metronome 46541751e
- Manpages got a lot of love and are now built from Markdown (Pieter Lexis)
- Move to PolarSSL base64 488360551 (Kees Monshouwer)
- The quiet=no query logging is now more informative 461df9d20
- We can finally bind to 0.0.0.0 and :: and guarantee answers from the correct source b71b60ee7
- We use per-packet timestamps to drop ancient traffic in case of overload b71b60ee7, non-Linux portability ind63f0d836
- Builtin webserver can be queried with the API key in the URL again c89f8cd02
- Ringbuffers are now available via API c89f8cd02
- Lua 5.3 compatibility 59c6fc3e3 (Kees Monshouwer)
- No longer leave a stale UNIX domain socket around from rec_control if the recursor was down 524e4f4d8, ticket #2061
- Running with ‘quiet=no’ would strangely actually prevent debug messages from being logged f48d7b657
- Webserver now implements CORS for the API ea89a97e8, fixing ticket #1984
- Houskeeping thread would sometimes run multiple times simultaneously, which worked, but was odd cc59bce67
root-nx-trustflag makes PowerDNS generalize NXDOMAIN responses from the root-servers 01402d568
getregisteredname()for Lua, which turns ‘www.bbc.co.uk’ into ‘bbc.co.uk’ 8cd4851be
- Lua preoutquery filter 3457a2a0e
- Lua IP-based filter (ipfilter) before parsing packets 4ea949413
iputilsclass for Lua, to quickly process IP addresses and netmasks in their native format
getregisterednamefunction for Lua, to find the registered domain for a given name
- Various new ringbuffers: top-servfail-remotes, top-largeanswer-remotes, top-servfail-queries
- Remove unneeded malloc traffic 93d4a8909 8682c32bc a903b39cf
- Our nameserver-loop detection carried around a lot of baggage for complex domain names, plus did not differentiate IPv4 and IPv6 well enough 891fbf888
- Prioritize new queries over nameserver responses, improving latency under query bursts bf3b0cec3
- Remove escaping in case there was nothing to escape 83b746fd1
- Our logging infrastructure had a lot of locking d1449e4d0
- Reduce logging level of certain common messages, which locked up synchronously logging systems 854d44e31
- Add limit on total wall-clock time spent on a query 9de3e0340
- Packet cache is now case-insensitive, which increases hitrate 90974597a
- Check for PIE, RELRO and stack protector during configure 8d0354b18 (Aki Tuomi)
- Testing for support of PIE etc was improved in b2053c28c and beyond, fixes #2125 (Ruben Kerkhof)
- Max query-per-query limit (max-qperq) is now configurable 173d790ea
- IPv6 outgoing queries had a disproportionate effect on our query load. Fixed in 76f190f2a and beyond.
- rec_control gave incorrect output on a timeout 12997e9d8
- When using the webserver AND having an error in the Lua script, recursor could crash during startup 62f0ae629
- Hugely long version strings would trip up security polling 18b733382 (Kees Monshouwer)
- The ‘remotes’ ringbuffer was sized incorrectly f8f243b01
- Cache sizes had an off-by-one scaling problem, with the wrong number of entries allocated per thread f8f243b01
- Our automatic file descriptor limit raising was attempted after setuid, which made it a lot less effective. Found and fixed by Aki Tuomi a6414fdce
- Timestamps used for dropping packets were occasionaly wrong 183eb8774 and 4c4765c10 (RC2) with thanks to Winfried for debugging.
- In RC1, our new DoS protection measures would crash the Recursor if too many root servers were unreachable.6a6fb05ad. Debugging and testing by Fusl.
Various other documentation changes by Christian Hofstaedtler and Ruben Kerkhof. Lots of improvements all over the place by Kees Monshouwer.