The Makefile isn't perfect. I noted it doesn't clean the bench,
but we have the same problem for some other parts, e.g. in deckard.

add option to reorder cached RRs in answers

Fixes https://gitlab.labs.nic.cz/knot/resolver/issues/93.
API of a KR_EXPORT function is changed, so ABIVER is bumped.

See merge request !47

Improve version.mk

See merge request !61

Fixes https://gitlab.labs.nic.cz/knot/resolver/issues/93.
API of a KR_EXPORT function is changed, so ABIVER is bumped.

daemon: another UINT_MAX -> UINT32_MAX



See merge request !58

daemon: some minor coverity scan issues were fixed



See merge request !49

Remove sandbox.lua from .gitignore



See merge request !56

Resolve libknot and libzscanner SONAME at the build time and fixes to bootstrap-depends.sh script

The OS X build is still failing, but it's unrelated to these changes.

See merge request !55

and set libknot_SONAME and libzscanner_SONAME as lua literals.

Remove now obsolete libpath lua function - use find_soname from
platform.mk to define <arg>_SONAME, add lua_pushliteral to
daemon/engine.c and add -D to daemon/daemon.mk for any new library
loaded from Lua.

Early awareness notification: a new lua module `version`
to periodically check for newer version on server and for CVE.

See merge request !52

Also avoid that extremely long line.

worker: avoid uninitialized pointers

The cookie module could segfault due to the `opt` pointer not being initialized when no EDNS was sent in the incoming request.

See merge request !53

The cookie module could segfault due to the `opt` pointer not being
initialized when no EDNS was sent in the incoming request.

Fix documentation example for using resolve() function.



See merge request !51

Michal Karm Babacek authored 8 years ago and Ondřej Surý committed 8 years ago

Based on [issue 28](https://github.com/CZ-NIC/knot-resolver/issues/28), we were able to boost kresd performance running in a Docker container on DockerCloud by nearly 100% by binding to a single interface:ipaddress. It might be handy for other users to know.

net.listen: make it more flexible

As noted in #94, it feels natural to call it like:
``net.listen({net.lo, '192.168.1.1'})``
Also minor fixes were done in that function and corresponding docs.

See merge request !46

Assortment of unimportant changes that I created during trying to understand how the whole resolution process works. Best read each commit separately.

As noted in #94, it feels natural to call it like:
``net.listen({net.lo, '192.168.1.1'})``
Also, minor fixes were done in that function and corresponding docs.