Modern, advanced and high performance authoritative-only nameserver
The PowerDNS Nameserver is a modern, advanced and high performance
authoritative-only nameserver. It is written from scratch and conforms
to all relevant DNS standards documents. Furthermore, PowerDNS
interfaces with almost any database.
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Leap:15.2/pdns && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| README.opendbx | 0000010036 9.8 KB | |
| pdns-4.0.3_allow_dacoverride_in_capset.patch | 0000000992 992 Bytes | |
| pdns-4.1.5.tar.bz2 | 0001116238 1.06 MB | |
| pdns-4.1.5.tar.bz2.sig | 0000000310 310 Bytes | |
| pdns.changes | 0000049836 48.7 KB | |
| pdns.keyring | 0000010504 10.3 KB | |
| pdns.spec | 0000014141 13.8 KB | |
| rcpdns | 0000012587 12.3 KB |
Revision 24 (latest revision is 32)
Yuchen Lin (maxlin_factory)
accepted
request 669043
from
Adam Majer (adamm)
(revision 24)
- Update to 4.1.5
* Improvements
- Apply alias scopemask after chasing
- Release memory in case of error in the openssl ecdsa constructor
- Switch to devtoolset 7 for el6
* Bug Fixes
- Crafted zone record can cause a denial of service
(bsc#1114157, CVE-2018-10851)
- Packet cache pollution via crafted query
(bsc#1114169, CVE-2018-14626)
- Fix compilation with libressl 2.7.0+
- Actually truncate truncated responses
- Update to 4.1.4
- Improvements
* #6590: Fix warnings reported by gcc 8.1.0.
* #6632, #6844, #6842, #6848: Make the gmysql backend future-proof
* #6685, #6686: Initialize some missed qtypes.
- Bug Fixes
* #6780: Avoid concurrent records/comments iteration from
running out of sync.
* #6816: Fix a crash in the API when adding records.
* #4457, #6691: pdns_control notify: handle slave without
renotify properly.
* #6736, #6738: Reset the TSIG state between queries.
* #6857: Remove SOA-check backoff on incoming notify and fix
lock handling.
* #6858: Fix an issue where updating a record via DNS-UPDATE in
a child zone that also exists in the parent zone, we would
incorrectly apply the update to the parent zone.
Comments 0