]> git.ipfire.org Git - thirdparty/knot-resolver.git/commitdiff
release 6.4.2 docs-release-6-4-185ey0/deployments/9752 1882/head
authorAleš Mrázek <ales.mrazek@nic.cz>
Wed, 5 Aug 2026 08:34:06 +0000 (10:34 +0200)
committerAleš Mrázek <ales.mrazek@nic.cz>
Wed, 5 Aug 2026 08:44:08 +0000 (10:44 +0200)
NEWS
doc/_static/config.schema.json
meson.build
pyproject.toml
python/knot_resolver/constants.py
setup.py

diff --git a/NEWS b/NEWS
index 487dd23db1c2116d543badb02855b19af43acc46..50c99ecde8df9f0ccf1af8933dd897032ff75877 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -1,4 +1,4 @@
-Knot Resolver 6.4.2 (2026-08-dd)
+Knot Resolver 6.4.2 (2026-08-05)
 ================================
 
 Bugfixes
index 8ccf19ba0c08e6e84362b406b24277a5e130b4e1..75b65cfa8ccc89f8a4d1537a129dba03e34ba8d1 100644 (file)
@@ -1,8 +1,8 @@
 {
     "$schema": "https://json-schema.org/draft/2020-12/schema",
-    "$id": "https://www.knot-resolver.cz/documentation/v6.4.1/_static/config.schema.json",
+    "$id": "https://www.knot-resolver.cz/documentation/v6.4.2/_static/config.schema.json",
     "title": "Knot Resolver configuration JSON schema",
-    "description": "Version Knot Resolver 6.4.1",
+    "description": "Version Knot Resolver 6.4.2",
     "type": "object",
     "properties": {
         "version": {
index f0c60e9ad45fc78e8bd0b114099ac617cdfab9f2..efeeb98b5b3e9a7df20814d8e3cf809bd4ba9678 100644 (file)
@@ -4,7 +4,7 @@ project(
   'knot-resolver',
   ['c', 'cpp'],
   license: 'GPLv3+',
-  version: '6.4.1',
+  version: '6.4.2',
   default_options: ['c_std=gnu11', 'b_ndebug=true'],
   meson_version: '>=0.53',
 )
index e0857c5ec34d92df82e4b9d11533cd8eca9b6de7..3aa0c62e1164a47c5a98b6d52e27278f062e975f 100644 (file)
@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "knot-resolver"
-version = "6.4.1"
+version = "6.4.2"
 description = "Knot Resolver Manager - a Python program that automatically manages the other components of the resolver"
 license = "GPL-3.0-or-later"
 authors = [
index 9adbc43edfd5b426e363970a96d66c06db94c4af..b1b947e5b4a3ff63b522f93d4aa71e6833f46c8d 100644 (file)
@@ -3,7 +3,7 @@ import platform
 import re
 from pathlib import Path
 
-VERSION = "6.4.1"
+VERSION = "6.4.2"
 USER = "knot-resolver"
 GROUP = "knot-resolver"
 
index 42c445ef9fc11e8b873ca4620544084f840539e2..e858455381a45811799cc4a813aee5b79becd752 100644 (file)
--- a/setup.py
+++ b/setup.py
@@ -36,7 +36,7 @@ entry_points = \
 
 setup_kwargs = {
     'name': 'knot-resolver',
-    'version': '6.4.1',
+    'version': '6.4.2',
     'description': 'Knot Resolver Manager - a Python program that automatically manages the other components of the resolver',
     'long_description': "# Knot Resolver\n\n[![Build Status](https://gitlab.nic.cz/knot/knot-resolver/badges/nightly/pipeline.svg?x)](https://gitlab.nic.cz/knot/knot-resolver/commits/nightly)\n[![Coverage Status](https://gitlab.nic.cz/knot/knot-resolver/badges/nightly/coverage.svg?x)](https://www.knot-resolver.cz/documentation/latest)\n[![Packaging status](https://repology.org/badge/tiny-repos/knot-resolver.svg)](https://repology.org/project/knot-resolver/versions)\n\nKnot Resolver is a full caching DNS resolver implementation. The core architecture is tiny and efficient, written in C and [LuaJIT][luajit], providing a foundation and a state-machine-like API for extension modules. There are three built-in modules - *iterator*, *validator* and *cache* - which provide the main functionality of the resolver. A few other modules are automatically loaded by default to extend the resolver's functionality.\n\nSince Knot Resolver version 6, it also includes a so-called [manager][manager]. It is a new component written in [Python][python] that hides the complexity of older versions and makes it more user friendly. For example, new features include declarative configuration in YAML format and HTTP API for dynamic changes in the resolver and more.\n\nKnot Resolver uses a [different scaling strategy][scaling] than the rest of the DNS resolvers - no threading, shared-nothing architecture (except MVCC cache which can be shared), which allows you to pin workers to available CPU cores and grow by self-replication. You can start and stop additional workers based on the contention without downtime, which is automated by the [manager][manager] by default.\n\nThe LuaJIT modules, support for DNS privacy and DNSSEC, and persistent cache with low memory footprint make it a great personal DNS resolver or a research tool to tap into DNS data. Strong filtering rules, and auto-configuration with etcd make it a great large-scale resolver solution. It also has strong support for DNS over TCP, in particular TCP Fast-Open, query pipelining and deduplication, and response reordering.\n\nFor more on using the resolver, see the [User Documentation][doc]. See the [Developer Documentation][doc-dev] for detailed architecture and development.\n\n## Packages\n\nThe latest stable packages for various distributions are available in our\n[upstream repository](https://pkg.labs.nic.cz/doc/?project=knot-resolver).\nFollow the installation instructions to add this repository to your system.\n\nKnot Resolver is also available from the following distributions' repositories:\n\n* [Fedora and Fedora EPEL](https://src.fedoraproject.org/rpms/knot-resolver)\n* [Debian stable](https://packages.debian.org/stable/knot-resolver),\n  [Debian testing](https://packages.debian.org/testing/knot-resolver),\n  [Debian unstable](https://packages.debian.org/sid/knot-resolver)\n* [Ubuntu](https://packages.ubuntu.com/jammy/knot-resolver)\n* [Arch Linux](https://archlinux.org/packages/extra/x86_64/knot-resolver/)\n* [Alpine Linux](https://pkgs.alpinelinux.org/packages?name=knot-resolver)\n\n### Packaging\n\nThe project uses [`apkg`](https://gitlab.nic.cz/packaging/apkg) for packaging.\nSee [`distro/README.md`](distro/README.md) for packaging specific instructions.\n\n## Building from sources\n\nKnot Resolver mainly depends on [KnotDNS][knot-dns] libraries, [LuaJIT][luajit], [libuv][libuv] and [Python][python].\n\nSee the [Building project][build] documentation page for more information.\n\n## Running\n\nBy default, Knot Resolver comes with [systemd][systemd] integration and you just need to start its service. It requires no configuration changes to run a server on localhost.\n\n```\n# systemctl start knot-resolver\n```\n\nSee the documentation at [knot-resolver.cz/documentation/latest][doc] for more information.\n\n## Running the Docker image\n\nRunning the Docker image is simple and doesn't require any dependencies or system modifications, just run:\n\n```\n$ docker run -Pit cznic/knot-resolver\n```\n\nThe images are meant as an easy way to try the resolver, and they're not designed for production use.\n\n## Contacting us\n\n- [GitLab issues](https://gitlab.nic.cz/knot/knot-resolver/issues) (you may authenticate via GitHub)\n- [mailing list](https://lists.nic.cz/postorius/lists/knot-resolver-announce.lists.nic.cz/)\n- [![Join the chat at https://gitter.im/CZ-NIC/knot-resolver](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/CZ-NIC/knot-resolver?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)\n\n[build]: https://www.knot-resolver.cz/documentation/latest/dev/build.html\n[doc]: https://www.knot-resolver.cz/documentation/latest/\n[doc-dev]: https://www.knot-resolver.cz/documentation/latest/dev\n[knot-dns]: https://www.knot-dns.cz/\n[luajit]: https://luajit.org/\n[libuv]: http://libuv.org\n[python]: https://www.python.org/\n[systemd]: https://systemd.io/\n[scaling]: https://www.knot-resolver.cz/documentation/latest/config-multiple-workers.html\n[manager]: https://www.knot-resolver.cz/documentation/latest/dev/architecture.html\n",
     'author': 'Aleš Mrázek',