Source: knot-resolver Section: net Priority: optional Maintainer: Progress Linux Maintainers XSBC-Uploaders: Daniel Baumann XSBC-Original-Maintainer: knot-resolver packagers XSBC-Original-Uploaders: Ondřej Surý , Daniel Kahn Gillmor , Santiago Ruano Rincón , Jakub Ružička Bugs: mailto:maintainers@lists.progress-linux.org Build-Depends: debhelper-compat (= 13), dns-root-data, doxygen, gnutls-bin , knot-dnsutils , libcmocka-dev (>= 1.0.0), libedit-dev, libfstrm-dev, libgnutls28-dev, libknot-dev (>= 3.0.1), liblmdb-dev, libluajit-5.1-dev, libnghttp2-dev, libprotobuf-c-dev, libsystemd-dev (>= 227) [linux-any], libuv1-dev, lua-basexx, lua-cqueues, luajit, meson, ninja-build, po-debconf, pkg-config, protobuf-c-compiler, python3-breathe, python3-sphinx, python3-sphinx-rtd-theme, socat Standards-Version: 4.5.1 Homepage: https://www.knot-resolver.cz/ Vcs-Browser: https://git.progress-linux.org/packages/fuchur/knot-resolver Vcs-Git: https://git.progress-linux.org/packages/fuchur/knot-resolver XSBC-Original-Vcs-Browser: https://salsa.debian.org/dns-team/knot-resolver XSBC-Original-Vcs-Git: https://salsa.debian.org/dns-team/knot-resolver.git Rules-Requires-Root: no Package: knot-resolver # Doesn't build on s390x due to missing luajit # https://github.com/LuaJIT/LuaJIT/issues/397 Architecture: amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64 ppc64el Depends: adduser, debconf, dns-root-data, lua-sec, lua-socket, ${misc:Depends}, ${shlibs:Depends} Replaces: libkres9 (<< 3.2.1-2) Breaks: libkres9 (<< 3.2.1-2) Recommends: knot-resolver-module-http, lua-basexx, lua-cqueues Description: caching, DNSSEC-validating DNS resolver The Knot 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. Package: knot-resolver-module-http Architecture: amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64 ppc64el Depends: fonts-glyphicons-halflings, libjs-bootstrap, libjs-d3, libjs-jquery, lua-http, lua-mmdb, ${misc:Depends}, ${shlibs:Depends} Breaks: knot-resolver-module-tinyweb (<< 1.1.0~git20160713-1~) Description: HTTP module for Knot Resolver The Knot 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. . This package contains HTTP module for local visualization of the resolver cache and queries. Package: knot-resolver-doc Architecture: all Multi-Arch: foreign Section: doc Depends: libjs-jquery, libjs-underscore, ${misc:Depends} Description: Documentation for Knot Resolver The Knot 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. . This package contains Knot Resolver Documentation.