Re: [knot-dns-users] Knot DNS 1.5.0 first release candidate!

Here are the correct links for those baffled by my (admittedly) poor mail formatting skills. Changelog: https://gitlab.labs.nic.cz/labs/knot/blob/v1.5.0-rc1/NEWS Sources: https://secure.nic.cz/files/knot-dns/knot-1.5.0-rc1.tar.gz https://secure.nic.cz/files/knot-dns/knot-1.5.0-rc1.tar.xz GPG signatures: https://secure.nic.cz/files/knot-dns/knot-1.5.0-rc1.tar.gz.asc https://secure.nic.cz/files/knot-dns/knot-1.5.0-rc1.tar.xz.asc Marek -- Marek Vavrusa, Knot DNS CZ.NIC Labs http://www.knot-dns.cz ------------------------------------------- Americká 23, 120 00 Praha 2, Czech Republic WWW: http://labs.nic.cz http://www.nic.cz On 3 June 2014 20:10, Marek Vavruša <marek.vavrusa(a)nic.cz> wrote: thought candidate. file, looking back of the new a few times. it appears it doesn't changes in between the versions benchmark of 1M small zones to our benchmark [1], which showed how much memory did we need per each zone). other features, we still managed to cut down the resource requirements for TLD use cases for about 20%. steep release-over-release tendency of smaller memory footprint and faster startup/answer performance just shows the unrelenting attention to the seemingly insignificant stuff, like structure alignment or packet distribution. That's what we're commited to. under the bonnet earlier this processing, which allowed us to do several cool things. The query processing is broken down to the set of step, modules. forward/reverse records according to the configuration template. This for example solves the IPv6 reverse records problem (SLAAC as well), as we don't have to generate massive zones, but rather create the records on the fly. [2]? It's a pretty ingenious solution to the fine-grained capture of the DNS traffic without compromising the performance. capture or replay queries now. 12K LOC less) the core functionality and extend the server at the some time. Think RRL, load balancing, geo-aware answers. multi-master failover, improved logs, asynchronously loaded zones, much more accurate "knotc memstats" and "zonestatus" tools, new user manual ... out the changelog to know more. That being said, I'd like to ask your help. The new stuff, like the asynchronous zone loading or logging, change the usability a little. Did we break your scripts or use case? Compliment, cheeky remark or angry rant? Please let us know, we'd like to get most of the kinks ironed out till the final release. Thank you.