A highly DNS-, DoS- and abuse-aware loadbalancer
http://www.powerdns.com/
dnsdist is a highly DNS-, DoS- and abuse-aware loadbalancer. Its goal in life
is to route traffic to the best server, delivering top performance to
legitimate users while shunting or blocking abusive traffic.
dnsdist is dynamic, in the sense that its configuration can be changed at
runtime, and that its statistics can be queried from a console-like interface.
- Devel package for openSUSE:Factory
-
2
derived packages
- Links to openSUSE:Factory / dnsdist
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout server:dns/dnsdist && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
_constraints | 0000000108 108 Bytes | |
_link | 0000000124 124 Bytes | |
dnsdist-1.9.4.tar.bz2 | 0001591994 1.52 MB | |
dnsdist-1.9.4.tar.bz2.sig | 0000000337 337 Bytes | |
dnsdist.changes | 0000024668 24.1 KB | |
dnsdist.keyring | 0000024519 23.9 KB | |
dnsdist.lua | 0000000336 336 Bytes | |
dnsdist.spec | 0000005003 4.89 KB | |
dnsdist.user | 0000000067 67 Bytes | |
local.usr.sbin.dnsdist | 0000000000 0 Bytes | |
usr.sbin.dnsdist | 0000000355 355 Bytes |
Revision 64 (latest revision is 69)
Adam Majer (adamm)
committed
(revision 64)
- update to 1.9.4: (bsc#1224001, CVE-2024-25581) * Fix “C++ One Definition Rule” warnings in XSK * Fix DNS over plain HTTP broken by reloadAllCertificates() * Fix a crash in incoming DoH with nghttp2 * Fix handling of XFR requests over DoH - changes since 1.9.0: * Support “no server available” result from Lua FFI load-balancing policies * Release incoming TCP connection right away on backend failure * Use server preference algorithm for ALPN selection * Fix a null-deref in incoming DNS over HTTPS with the nghttp2 provider * Fix DNS over HTTP connections/queries counters with the nghttp2 provider * Fix first IPv6 console connection being rejected * Fix XSK-enabled check when reconnecting a backend * Properly handle a failure of the first lazy health-check * Also handle EHOSTUNREACH as a case for reconnecting the socket
Comments 0