Skip to content
Snippets Groups Projects
user avatar
Marek Vavruša authored
this fixes a bug when a text-declared type wasn’t reused and LJ eventually segfaulted in ffi.new after a lot of redeclarations
671bf0f5
Forked from Knot projects / Knot Resolver
7852 commits behind the upstream repository.

Knot DNS Resolver

Build Status Coverage Status Coverity Documentation Status

The Knot DNS Resolver is a caching full resolver implementation written in C and LuaJIT, including both a resolver library and a daemon. Modular architecture of the library keeps the core tiny and efficient, and provides a state-machine like API for extensions. There are three built-in modules - iterator, cache, validator, and many external.

The Lua modules, switchable and shareable cache, and fast FFI bindings makes it great to tap into resolution process, or be used for your recursive DNS service. It's the OpenResty of DNS.

The server adopts a different scaling strategy than the rest of the DNS recursors - no threading, shared-nothing architecture (except MVCC cache that may be shared). You can start and stop additional nodes depending on the contention without downtime.

Try it out?

Keep in mind that the Knot DNS Resolver is in beta. While it's being tested by the DNS test harness, we'll be super glad to hear out your feedback!

Building from sources

The Knot DNS Resolver depends on the 2.0.1 version of the Knot DNS library, LuaJIT and libuv. See the Building project documentation page for more information.

Docker image

This is simple and doesn't require any dependencies or system modifications, just run:

$ docker run cznic/knot-resolver

See the build page registry.hub.docker.com/u/cznic/knot-resolver for more information and options.

Running

The project builds a resolver library in the lib directory, and a daemon in the daemon directory.

$ kresd -h

See the documentation at knot-resolver.readthedocs.org.

Contacting us

Join the chat at https://gitter.im/CZ-NIC/knot-resolver