Ubuntu
knot-resolver package

knot-resolver 1.0.0~beta3-1 source package in Ubuntu

Changelog

knot-resolver (1.0.0~beta3-1) unstable; urgency=medium

  * Add lua-socket and lua-sec for root TA bootstrapping
  * Imported Upstream version 1.0.0~beta3

 -- Ondřej Surý <email address hidden>  Sat, 30 Jan 2016 16:15:23 +0100

Upload details

Uploaded by:
Debian DNS Maintainers
Uploaded to:
Sid
Original maintainer:
Debian DNS Maintainers
Architectures:
any
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Xenial release universe misc

Downloads

File Size SHA-256 Checksum
knot-resolver_1.0.0~beta3-1.dsc 2.4 KiB f0512798c158a5bccf1a3acf37e87c5330e2c1b5492d5f12a6c5499d97492d9c
knot-resolver_1.0.0~beta3.orig.tar.xz 425.6 KiB 8c6ee05babc456697e1c1957ee77f60bd309b908319a566bca23440041cb0059
knot-resolver_1.0.0~beta3-1.debian.tar.xz 189.4 KiB 2a5dcf82bd1347cfce5226fb8614f0abab916424d7320ac41485b4490217b0c9

No changes file available.

Binary packages built by this source

knot-resolver: No summary available for knot-resolver in ubuntu yakkety.

No description available for knot-resolver in ubuntu yakkety.

knot-resolver-dbg: No summary available for knot-resolver-dbg in ubuntu yakkety.

No description available for knot-resolver-dbg in ubuntu yakkety.

knot-resolver-dbgsym: debug symbols for package knot-resolver

 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.