This is release 4.8.4 of the Authoritative Server.
Please review the Upgrade Notes before upgrading from versions < 4.8.x.
Add supervisor to Auth container image¶
References: pull request 13625
extend the systemd startup timeout during lmdb schema migrations¶
References: pull request 13626
ixfrdist: Fix the validation of ‘max-soa-refresh’¶
References: pull request 13624
This is release 4.8.3 of the Authoritative Server.
Please review the Upgrade Notes before upgrading from versions < 4.8.x.
This release contains one new feature (default-catalog-zone
), one bugfix (in ixfrdist), and a workaround for a bug in the MySQL client libraries.
add default-catalog-zone setting¶
References: pull request 13240
smysql: stop explicitly setting MYSQL_OPT_RECONNECT to 0¶
References: pull request 13271
ixfrdist: set AA=1 on SOA responses¶
References: pull request 13316
This is release 4.8.2 of the Authoritative Server.
Please review the Upgrade Notes before upgrading from versions < 4.8.x.
This release contains a small collection of fixes:
(I)XFR: handle partial read of len prefix¶
References: pull request 13186
fix code producing json¶
References: pull request 13187
calidns: fix setting an ECS source of 0¶
References: pull request 13188
Fix incorrect optsize¶
References: pull request 13189
lmdb: when broadcasting indexes, -do- rewrite them even if they are unchanged¶
References: pull request 13099
This is release 4.8.1 of the Authoritative Server.
Please review the Upgrade Notes before upgrading from versions < 4.8.x.
This release contains a small collection of fixes:
lmdb: add backend commands for checking & refreshing indexes¶
References: pull request 12997
lmdb: in Lightning Stream mode, during deleteDomain, use RW transaction to get ID list¶
References: pull request 12996
Stop using the now deprecated ERR_load_CRYPTO_strings() to detect OpenSSL¶
References: pull request 12993
Work around Red Hat 8 pooping the bed in OpenSSL’s headers¶
References: pull request 12991
YaHTTP: Prevent integer overflow on very 3large chunks¶
References: pull request 12992
This is release 4.8.0 of the Authoritative Server.
Please review the Upgrade Notes before upgrading from versions < 4.8.x.
In 4.8, the LMDB backend gains a new Lightning Stream-compatible schema, which requires a data migration (this is automatic, and there is no migration back to the old schema). LMDB backend users should pay extra attention to the Upgrade Notes.
Lightning Stream is an open source data syncer that allows multiple nodes to sync LMDB (Lightning Memory-Mapped Database) data to and from an S3 (compatible) bucket. This has particular advantages in distributed and/or large-scale applications (i.e. ~1 million records), making DNS replication much, much easier to manage.
We are excited about how Lightning Stream simplifies running multiple distributed PowerDNS Authoritative servers, with full support for keeping record data and DNSSEC keys in sync, from multiple writers.
4.8.0 improves the handling of accidental duplicate domains – deleting a zone now deletes all versions of it. This release also contains a few other fixes, please see the list below.
do not answer with broken TYPE0 data when expanding an ENT wildcard¶
References: pull request 12869
lmdb: delete duplicate domain entries in deleteDomain¶
References: pull request 12872
pdnsutil: if user pushes unknown key in response to “problem with zone” prompt, do not throw away their changes¶
References: pull request 12868
add setting workaround-11804-max-chunk-records¶
References: pull request 12828
This is release 4.8.0-beta1 of the Authoritative Server.
Please review the Upgrade Notes before upgrading from versions < 4.8.x.
In 4.8, the LMDB backend gains a new Lightning Stream-compatible schema, which requires a data migration (this is automatic, and there is no migration back to the old schema). LMDB backend users should pay extra attention to the Upgrade Notes.
Lightning Stream is an open source data syncer that allows multiple nodes to sync LMDB (Lightning Memory-Mapped Database) data to and from an S3 (compatible) bucket. This has particular advantages in distributed and/or large-scale applications (i.e. ~1 million records), making DNS replication much, much easier to manage.
We are excited about how Lightning Stream simplifies running multiple distributed PowerDNS Authoritative servers, with full support for keeping record data and DNSSEC keys in sync, from multiple writers.
4.8.0-beta1 adds logic to deal with domains existing twice in the database when two Lightning Stream nodes manage to add it at the same time. It also contains a few other fixes, please see the list below.
ixfrdist: add a per domain max-soa-refresh option¶
References: pull request 12768
LUA records: enhance ifportup() with lists of sets of addresses like ifurlup()¶
References: pull request 12669
lmdb: handle lack of support for RRset comments better¶
References: pull request 12636
calm down the communicator loop (Kees Monshouwer)¶
References: pull request 12721
DNSRecord: Ensure that the content can be read or replaced, not edited¶
References: pull request 12664
LMDB: handle duplicate domain existence consistently¶
References: pull request 12729
Pick the right signer name when a NSEC name is also a delegation point (Kees Monshouwer)¶
References: pull request 12740
Fixes a typo in pdnsutil clear-zone help output (san983)¶
References: pull request 12706
This is release 4.8.0-alpha1 of the Authoritative Server.
Please review the Upgrade Notes before upgrading from versions < 4.8.x.
In this release, the LMDB backend gains a new Lightning Stream-compatible schema, which requires a data migration (this is automatic, and there is no migration back to the old schema). LMDB backend users should pay extra attention to the Upgrade Notes.
Lightning Stream is an open source data syncer that allows multiple nodes to sync LMDB (Lightning Memory-Mapped Database) data to and from an S3 (compatible) bucket. This has particular advantages in distributed and/or large-scale applications (i.e. ~1 million records), making DNS replication much, much easier to manage.
We are excited about how Lightning Stream simplifies running multiple distributed PowerDNS Authoritative servers, with full support for keeping record data and DNSSEC keys in sync, from multiple writers.
This version also contains various other small fixes and improvements. Except for very minor ones, they are listed below.
new lmdbbackend storage schema that is compatible with Lightning Stream¶
References: pull request 12546
add byteslimit support to lua ifurlup() function¶
References: pull request 12277
pdnsutil, implement list-member-zones (Kees Monshouwer)¶
References: pull request 12406
LUA: accept more hex formats in createForward[6]¶
References: pull request 12349
cleanup for OpenSSL 3.0 API¶
References: pull request 11600, pull request 12401, pull request 12414, pull request 12423, pull request 12462, pull request 12501, pull request 12502, pull request 12513, pull request 12515, pull request 12516, pull request 12524, pull request 12527, pull request 12540, pull request 12550
service files: Add more sandboxing options¶
References: pull request 11065
move alsoNotifies up into DNSBackend¶
References: pull request 12265
Basic abstraction for handling colored terminal output, respecting isatty(), –no-colors and NO_COLOR¶
References: pull request 11346
change sdig output order (Kees Monshouwer)¶
References: pull request 11858
save errno value as close(2) might clobber it¶
References: pull request 11101
Fix multiple-version IXFR request handling in ixfrdist (Håkan Lindqvist)¶
References: pull request 12127
Properly encode json strings containing binary data¶
References: pull request 12260
lmdb, fix TSIG key removal (Kees Monshouwer)¶
References: pull request 12322
Update supported record types: remove A6 MAILA MAILB SIG and WKS, add ZONEMD¶
References: pull request 12252
Detect invalid bytes in makeBytesFromHex()¶
References: pull request 12066
initialize zone cache after dropping privileges (Kees Monshouwer)¶
References: pull request 11908
Prevent a race during the processing of SVC auf-hints¶
References: pull request 12659
fix ColumnSize argument in SQLBindParameter #12324 (v1shnya)¶
References: pull request 12331