--- - branch: MAIN date: Wed Nov 16 13:47:38 UTC 2022 files: - new: '1.49' old: '1.48' path: pkgsrc/net/bind916/Makefile pathrev: pkgsrc/net/bind916/Makefile@1.49 type: modified - new: '1.42' old: '1.41' path: pkgsrc/net/bind916/distinfo pathrev: pkgsrc/net/bind916/distinfo@1.42 type: modified id: 20221116T134738Z.70ca51c0e317317266198001124c562ad5633ea6 log: | net/bind916: update to 9.16.35 9.6.35 (2022-11-16) Bug Fixes * A crash was fixed that happened when a dnssec-policy zone that used NSEC3 was reconfigured to enable inline-signing. [GL #3591] * In certain resolution scenarios, quotas could be erroneously reached for servers, including any configured forwarders, resulting in SERVFAIL answers being sent to clients. This has been fixed. [GL #3598] * rpz-ip rules in response-policy zones could be ineffective in some cases if a query had the CD (Checking Disabled) bit set to 1. This has been fixed. [GL #3247] * Previously, if Internet connectivity issues were experienced during the initial startup of named, a BIND resolver with dnssec-validation set to auto could enter into a state where it would not recover without stopping named, manually deleting the managed-keys.bind and managed-keys.bind.jnl files, and starting named again. This has been fixed. [GL #2895] * The statistics counter representing the current number of clients awaiting recursive resolution results (RecursClients) could overflow in certain resolution scenarios. This has been fixed. [GL #3584] * Previously, BIND failed to start on Solaris-based systems with hundreds of CPUs. This has been fixed. [GL #3563] * When a DNS resource record's TTL value was equal to the resolver's configured prefetch "eligibility" value, the record was erroneously not treated as eligible for prefetching. This has been fixed. [GL #3603] module: pkgsrc subject: 'CVS commit: pkgsrc/net/bind916' unixtime: '1668606458' user: taca