Index index by Group index by Distribution index by Vendor index by creation date index by Name Mirrors Help Search

bind-utils-9.16.42-5.28.1 RPM for armv7hl

From OpenSuSE Ports Leap 15.5 for armv7hl

Name: bind-utils Distribution: openSUSE Step 15
Version: 9.16.42 Vendor: openSUSE
Release: 5.28.1 Build date: Wed Jun 28 15:47:40 2023
Group: Productivity/Networking/DNS/Utilities Build host: armbuild21
Size: 5122413 Source RPM: bind-9.16.42-5.28.1.src.rpm
Summary: Libraries for "bind" and utilities to query and test DNS
This package includes the utilities "host", "dig", and "nslookup" used to
test and query the Domain Name System (DNS) and also the libraries rquired
for the base "bind" package. The Berkeley Internet
Name Domain (BIND) DNS server is found in the package named bind.






* Wed Jun 21 2023
  - Update to release 9.16.42
    Security Fixes:
    * The overmem cleaning process has been improved, to prevent the
      cache from significantly exceeding the configured
      max-cache-size limit. (CVE-2023-2828)
    * A query that prioritizes stale data over lookup triggers a
      fetch to refresh the stale data in cache. If the fetch is
      aborted for exceeding the recursion quota, it was possible for
      named to enter an infinite callback loop and crash due to stack
      overflow. This has been fixed. (CVE-2023-2911)
    Bug Fixes:
    * Previously, it was possible for a delegation from cache to be
      returned to the client after the stale-answer-client-timeout
      duration. This has been fixed.
    [bsc#1212544, bsc#1212567, jsc#SLE-24600]
* Wed May 17 2023
  - Update to release 9.16.41
    Bug Fixes:
    * When removing delegations from an opt-out range,
      empty-non-terminal NSEC3 records generated by those delegations
      were not cleaned up. This has been fixed.
* Tue Apr 25 2023
  - Update to release 9.16.40
    Bug Fixes:
    * Logfiles using timestamp-style suffixes were not always
      correctly removed when the number of files exceeded the limit
      set by versions. This has been fixed for configurations which
      do not explicitly specify a directory path as part of the file
      argument in the channel specification.
    * Performance of DNSSEC validation in zones with many DNSKEY
      records has been improved.
* Wed Mar 15 2023
  - Update to release 9.16.39
    Feature Changes:
    * libuv support for receiving multiple UDP messages in a single
      recvmmsg() system call has been tweaked several times between
      libuv versions 1.35.0 and 1.40.0; the current recommended libuv
      version is 1.40.0 or higher. New rules are now in effect for
      running with a different version of libuv than the one used at
      compilation time. These rules may trigger a fatal error at
    - Building against or running with libuv versions 1.35.0 and
      1.36.0 is now a fatal error.
    - Running with libuv version higher than 1.34.2 is now a
      fatal error when named is built against libuv version
      1.34.2 or lower.
    - Running with libuv version higher than 1.39.0 is now a
      fatal error when named is built against libuv version
      1.37.0, 1.38.0, 1.38.1, or 1.39.0.
    * This prevents the use of libuv versions that may trigger an
      assertion failure when receiving multiple UDP messages in a
      single system call.
    Bug Fixes:
    * named could crash with an assertion failure when adding a new
      zone into the configuration file for a name which was already
      configured as a member zone for a catalog zone. This has been
    * When named starts up, it sends a query for the DNSSEC key for
      each configured trust anchor to determine whether the key has
      changed. In some unusual cases, the query might depend on a
      zone for which the server is itself authoritative, and would
      have failed if it were sent before the zone was fully loaded.
      This has now been fixed by delaying the key queries until all
      zones have finished loading.
* Thu Feb 16 2023
  - Update to release 9.16.38
    Bug Fixes:
    * A constant stream of zone additions and deletions via rndc
      reconfig could cause increased memory consumption due to
      delayed cleaning of view memory. This has been fixed.
    * The speed of the message digest algorithms (MD5, SHA-1, SHA-2),
      and of NSEC3 hashing, has been improved.
    * Building BIND 9 failed when the --enable-dnsrps switch for
      ./configure was used. This has been fixed.
  - Updated keyring and signature
* Tue Jan 24 2023
  - Update to release 9.16.37
    Security Fixes:
    * An UPDATE message flood could cause named to exhaust all
      available memory. This flaw was addressed by adding a new
      update-quota option that controls the maximum number of
      outstanding DNS UPDATE messages that named can hold in a queue
      at any given time (default: 100). (CVE-2022-3094)
    * named could crash with an assertion failure when an RRSIG query
      was received and stale-answer-client-timeout was set to a
      non-zero value. This has been fixed. (CVE-2022-3736)
    * named running as a resolver with the
      stale-answer-client-timeout option set to any value greater
      than 0 could crash with an assertion failure, when the
      recursive-clients soft quota was reached. This has been fixed.
    New Features:
    * The new update-quota option can be used to control the number
      of simultaneous DNS UPDATE messages that can be processed to
      update an authoritative zone on a primary server, or forwarded
      to the primary server by a secondary server. The default is
      100. A new statistics counter has also been added to record
      events when this quota is exceeded, and the version numbers for
      the XML and JSON statistics schemas have been updated.
    Feature Changes:
    * The Differentiated Services Code Point (DSCP) feature in BIND
      has been deprecated. Configuring DSCP values in named.conf now
      causes a warning to be logged. Note that this feature has only
      been partly operational since the new Network Manager was
      introduced in BIND 9.16.0.
    * The catalog zone implementation has been optimized to work with
      hundreds of thousands of member zones.
    Bug Fixes:
    * In certain query resolution scenarios (e.g. when following
      CNAME records), named configured to answer from stale cache
      could return a SERVFAIL response despite a usable, non-stale
      answer being present in the cache. This has been fixed.
    [bsc#1207471, bsc#1207473, bsc#1207475, jsc#SLE-24600]
* Thu Dec 22 2022
  - Update to release 9.16.36
    Feature Changes:
    * The auto-dnssec option has been deprecated and will be removed
      in a future BIND 9.19.x release. Please migrate to
    Bug Fixes:
    * When a catalog zone was removed from the configuration, in some
      cases a dangling pointer could cause the named process to
    * When a zone was deleted from a server, a key management object
      related to that zone was inadvertently kept in memory and only
      released upon shutdown. This could lead to constantly
      increasing memory use on servers with a high rate of changes
      affecting the set of zones being served.
    * In certain cases, named waited for the resolution of
      outstanding recursive queries to finish before shutting down.
    * The zone <name>/<class>: final reference detached log message
      was moved from the INFO log level to the DEBUG(1) log level to
      prevent the named-checkzone tool from superfluously logging
      this message in non-debug mode.
* Thu Nov 24 2022
  - Update to release 9.16.35
    Bug Fixes:
    * A crash was fixed that happened when a dnssec-policy zone that
      used NSEC3 was reconfigured to enable inline-signing.
    * In certain resolution scenarios, quotas could be erroneously
      reached for servers, including any configured forwarders,
      resulting in SERVFAIL answers being sent to clients.
    * rpz-ip rules in response-policy zones could be ineffective in
      some cases if a query had the CD (Checking Disabled) bit set to
    * 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.
    * The statistics counter representing the current number of
      clients awaiting recursive resolution results (RecursClients)
      could overflow in certain resolution scenarios.
    * Previously, BIND failed to start on Solaris-based systems with
      hundreds of CPUs.
    * 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.
* Fri Nov 11 2022
  - Update to release 9.16.34
    New Features:
    * Support for parsing and validating the dohpath service
      parameter in SVCB records was added.
    * named now logs the supported cryptographic algorithms during
      startup and in the output of named -V.
    Bug Fixes:
    * Changing just the TSIG key names for primaries in catalog
      zones’ member zones was not effective. This has been fixed.
    Known Issues:
    * Upgrading from BIND 9.16.32 or any older version may require a
      manual configuration change. The following configurations are
    - type primary zones configured with dnssec-policy but without
      either allow-update or update-policy,
    - type secondary zones configured with dnssec-policy.
      In these cases please add inline-signing yes; to the individual
      zone configuration(s). Without applying this change, named will
      fail to start. For more details, see
* Wed Sep 21 2022
  - Update to release 9.16.33
    Security Fixes:
    * Previously, there was no limit to the number of database lookups
      performed while processing large delegations, which could be
      abused to severely impact the performance of named running as a
      recursive resolver. This has been fixed. (CVE-2022-2795)
    * named running as a resolver with the stale-answer-client-timeout
      option set to 0 could crash with an assertion failure, when
      there was a stale CNAME in the cache for the incoming query.
      This has been fixed. (CVE-2022-3080)
    * A memory leak was fixed that could be externally triggered in the
      DNSSEC verification code for the ECDSA algorithm. (CVE-2022-38177)
    * Memory leaks were fixed that could be externally triggered in the
      DNSSEC verification code for the EdDSA algorithm. (CVE-2022-38178)
    Feature Changes:
    * Response Rate Limiting (RRL) code now treats all QNAMEs that are
      subject to wildcard processing within a given zone as the same
      name, to prevent circumventing the limits enforced by RRL.
    * Zones using dnssec-policy now require dynamic DNS or
      inline-signing to be configured explicitly.
    * A backward-compatible approach was implemented for encoding
      internationalized domain names (IDN) in dig and converting the
      domain to IDNA2008 form; if that fails,
      BIND tries an IDNA2003 conversion.
    Bug Fixes:
    * A serve-stale bug was fixed, where BIND would try to return stale
      data from cache for lookups that received duplicate queries or
      queries that would be dropped. This bug resulted in premature
      SERVFAIL responses, and has now been resolved.
    [bsc#1203614, bsc#1203618, bsc#1203619, bsc#1203620, jsc#SLE-24600]
* Fri Sep 09 2022
  - Add systemd drop-in directory for named service
    [bsc#1201689, bind.spec]
* Fri Sep 09 2022
  - Include a modified createNamedConfInclude script again, as this
    broke compatability with existing configurations.
    A symlink for named.conf.include to /var/lib/named is created to
    allow for a read-only /etc directory.
    However it is still advised to change the existing configuration.
    See README-bind.chrootenv for a guide how to do this.
    [bsc#1203250, vendor-files/tools/createNamedConfInclude,
    vendor-files/docu/README-bind.chrootenv, bind.spec]
* Tue Aug 23 2022
  - Update to release 9.16.32
    Feature Changes:
    * The DNSSEC algorithms RSASHA1 and NSEC3RSASHA1 are now automatically
    disabled on systems where they are disallowed by the security policy
    (e.g. Red Hat Enterprise Linux 9). Primary zones using those algorithms
    need to be migrated to new algorithms prior to running on these systems,
    as graceful migration to different DNSSEC algorithms is not possible when
    RSASHA1 is disallowed by the operating system.
    * Log messages related to fetch limiting have been improved to provide
    more complete information. Specifically, the final counts of allowed
    and spilled fetches are now logged before the counter object is destroyed.
    Bug Fixes:
    * Non-dynamic zones that inherit dnssec-policy from the view or options
    blocks were not marked as inline-signed and therefore never scheduled
    to be re-signed. This has been fixed.
    * The old max-zone-ttl zone option was meant to be superseded by
    the max-zone-ttl option in dnssec-policy; however, the latter option
    was not fully effective. This has been corrected: zones no longer load
    if they contain TTLs greater than the limit configured in dnssec-policy.
    For zones with both the old max-zone-ttl option and dnssec-policy
    configured, the old option is ignored, and a warning is generated.
    * rndc dumpdb -expired was fixed to include expired RRsets,
    even if stale-cache-enable is set to no and
    the cache-cleaning time window has passed.
    [bind-9.16.32.tar.xz, bind-9.16.32.tar.xz.sha512.asc,
    bind-9.16.31.tar.xz, bind-9.16.31.tar.xz.sha512.asc,
    bind.spec, jsc#SLE-24600]
* Thu Jul 14 2022
  - Update to release 9.16.31
    This is the first of monthly updates of "bind". It is planned
    to update bind when a new upstream maintennace release becomes
    available, which is usually towards the end of a month, see
    Compared to the previous SUSE release, in this release,
    53 (minor) bugs were fixed
    13 (minor) functional enhancements were made
    3 security issues are now fixed upstream:
      CVE-2022-0396, CVE-2021-25220, CVE-2021-25219
    plus a few minor changes.
    For a full list of changes, please refer to the
    CHANGES file in the source rpm.
    This update obsoletes the following patches:
    * bind-fix-build-with-older-sphinx.patch
    * bind-CVE-2021-25219.patch
    * bind-9.16.27-0001-CVE-2021-25220.patch
    * bind-9.16.27-0002-CVE-2022-0396.patch
    [bind-9.16.31.tar.xz, bind-9.16.31.tar.xz.sha512.asc,
    bind-9.16.20.tar.xz, bind-9.16.20.tar.xz.sha512.asc,
    bind-fix-build-with-older-sphinx.patch, bind-CVE-2021-25219.patch,
* Mon Jun 20 2022
  - When enabling query_logging by un-commenting an example in
    bind.conf, named attempts to create a file in /var/log which
    fails due to missing credentials. This also applies to the
    "dump-file" and the "statistics-file".
    This is solved by having systemd-tmpfiles create a subdirectory
    "/var/log/named" owned by named:named and changing the file
    paths accordingly:
    /var/log/named_querylog -> /var/log/named/querylog
    /var/log/named_dump.db -> /var/log/named/dump.db
    /var/log/named.stats -> /var/log/named/stats
    Also, in "named.service", the ReadWritePath was changed to
    include "/var/log/named" rather than just "var/log".
    [bsc#1200685, bind.spec, vendor-files/config/named.conf,
* Fri May 13 2022
  - A non-existent initialization script (eg a leftorver
    "createNamedConfInclude" in /etc/sysconfig/named) may cause named
    not to start. A warning message is printed in named.prep and
    the fact is ignored.
    Also, the return value of a failed script was not handled properly
    causing a failed script to not prevent named to start. This
    is now fixed properly.
    [bsc#1199044, vendor-files.tar.bz2]
* Thu Mar 17 2022
  - Obsolete bind-chrootenv as it is no longer needed.
    [bsc#1196990, bind.spec]
* Wed Mar 16 2022
  - * When using forwarders, bogus NS records supplied by, or via, those
      forwarders may be cached and used by named if it needs to recurse
      for any reason, causing it to obtain and pass on potentially
      incorrect answers. [CVE-2021-25220]
    * TCP connection slots may be consumed for an indefinite time frame
      via a specifically crafted TCP stream sent from a client.
      This issue can only be triggered on BIND servers which have
      keep-response-order enabled, which is not the default configuration.
      The keep-response-order option is an ACL block, and as such, any
      hosts specified within it will be able to trigger this issue on
      affected versions. [CVE-2022-0396]
    [CVE-2021-25220, bsc#1197135, bind-9.16.27-0001-CVE-2021-25220.patch
    CVE-2022-0396, bsc#1197136, bind-9.16.27-0002-CVE-2022-0396.patch]
* Wed Jan 19 2022
  - Added /var/log to the ReadWritePaths as some log files are
    written there:
    * dump-file "/var/log/named_dump.db"
    * statistics-file "/var/log/named.stats"
    [bsc#1194721, vendor-files.tar.bz2]
* Mon Jan 17 2022
  - Added "BuildRequires: python-rpm-macros". This was pulled in by
    python3 by mistake in the past and had been removed via Maintenance
    [bind.spec, bsc#1194746]
* Wed Nov 03 2021
  - Fixed CVE-2021-25219:
    The lame-ttl option controls how long named caches certain types
    of broken responses from authoritative servers (see the security
    advisory for details). This caching mechanism could be abused by
    an attacker to significantly degrade resolver performance. The
    vulnerability has been mitigated by changing the default value of
    lame-ttl to 0 and overriding any explicitly set value with 0,
    effectively disabling this mechanism altogether. ISC's testing has
    determined that doing that has a negligible impact on resolver
    performance while also preventing abuse.
    Administrators may observe more traffic towards servers issuing
    certain types of broken responses than in previous BIND 9 releases.
    [bsc#1192146, CVE-2021-25219, bind-CVE-2021-25219.patch]
* Tue Oct 19 2021
  - Upgrade of bind to 9.16.20.
    This upgrade has the following MAJOR changes:
    * it combines the various libraries into bind-utils as they
      are used only for bind itself.
    * the daemon is started using a systemd unit rather than a
      sysV init script
    * the system is protected against a misbehaving daemon not by
      putting the daemon into a chroot jail but by relying on systemd
    * it includes fixes for the following CVEs:
      + Fix off-by-one bug in ISC SPNEGO implementation.
      + Insufficient IXFR checks could result in named serving a
      zone without an SOA record at the apex, leading to a
      RUNTIME_CHECK assertion failure when the zone was
      subsequently refreshed. This has been fixed by adding an
      owner name check for all SOA records which are included
      in a zone transfer. (CVE-2021-25214)
      + named crashed when a DNAME record placed in the ANSWER
      section during DNAME chasing turned out to be the final
      answer to a client query. (CVE-2021-25215)
      + A specially crafted GSS-TSIG query could cause a buffer
      overflow in the ISC implementation of SPNEGO.  (CVE-2021-25216)
      + An assertion failure occurred when named attempted to send a
      UDP packet that exceeded the MTU size, if Response Rate
      Limiting (RRL) was enabled.  (CVE-2021-25218)
    * it obsoletes the following patches:
      + bind-Print-diagnostics-on-dns_name_issubdomain-failure-in.patch
      + bind-replace-varrun-with-run.patch
      + bind-CVE-2021-25214.patch
      + bind-CVE-2021-25215.patch
    * it brings with it this new patch:
      + bind-fix-build-with-older-sphinx.patch
    For more changes, see the CHANGES file in the src RPM.
    bind-replace-varrun-with-run.patch, bind-CVE-2021-25214.patch,
    bind-CVE-2021-25215.patch, bind-fix-build-with-older-sphinx.patch]
* Wed Jul 21 2021
  - Since BIND 9.9, it has been easier to use tsig-keygen and
    ddns-confgen to generare TSIG keys. In 9.13, TSIG support was
    removed from dnssec-keygen, so now it is just for DNSKEY (and KEY
    for obscure cases). tsig-keygen is now used to generate DDNS keys.
    [bsc#1187921, vendor-files.tar.bz2]
* Wed Apr 28 2021
  - * A broken inbound incremental zone update (IXFR)
      can cause named to terminate unexpectedly
      [CVE-2021-25214, bind-CVE-2021-25214.patch]
    * An assertion check can fail while answering queries
      for DNAME records that require the DNAME to be processed to resolve
      [CVE-2021-25215, bind-CVE-2021-25215.patch]
    * A second vulnerability in BIND's GSSAPI security
      policy negotiation can be targeted by a buffer overflow attack
      This does not affect this package as the affected code is
* Fri Apr 23 2021
  - pass PIE compiler and linker flags via environment variables to make
    /usr/bin/delv in bind-tools also position independent (bsc#1183453).
  - drop pie_compile.diff: no longer needed, this patch is difficult to
    maintain, the environment variable approach is less error prone.
    [bsc#1183453, bind.spec, pie_compile.diff]
* Wed Apr 21 2021
  - /var/run is deprecated, replaced by /run
    [bsc#1185073, bind-replace-varrun-with-run.patch,
    bind-chrootenv.conf, vendor-files.tar.bz2]
* Thu Nov 12 2020
  - Removed baselibs.conf as SLE does not distribute 32 bit libraries.
* Fri Nov 06 2020
  - Added special make instruction for the "Administrator Reference
    Manual" which is built using python3-Sphinx
    [bsc#1177983, bind.spec]
  - Removed "" from named.service as that
    leads to a systemd ordering cycle
    [bsc#1177491, bsc#1178626, bsc#1177991, vendor-files.tar.bz2]
* Tue Oct 27 2020
  - Add /usr/lib64/named to the files and directories in
    bind-chrootenv.conf. This directory contains plugins loaded
    after the chroot().
  - Replaced named's dependency on time-sync with a dependency on time-set
    in named.service. The former leads to a dependency-loop.
  - Removed "dnssec-enable" from named.conf as it has been obsoleted.
    Added a comment for reference which should be removed
    in the future.
  - Added a comment to the "dnssec-validation" in named.conf
    with a reference to forwarders which do not return signed responses.
  - Replaced an INSIST macro which calls abort with a test and a
    diagnostic output.
* Fri Sep 18 2020
  - Removed "-r /dev/urandom" from all invocations of rndc-confgen
    (init/named system/lwresd.init system/named.init in vendor-files)
    as this option is deprecated and causes rndc-confgen to fail.
    [bsc#1173311, bsc#1176674, bsc#1170713, vendor-files.tar.bz2]
* Tue Sep 15 2020
  - /usr/bin/genDDNSkey: Removing the use of the -r option in the call
    of /usr/sbin/dnssec-keygen as BIND now uses the random number
    functions provided by the crypto library (i.e., OpenSSL or a
    PKCS#11 provider) as a source of randomness rather than /dev/random.
    Therefore the -r command line option no longer has any effect on
    dnssec-keygen. Leaving the option in genDDNSkey as to not break
    compatibility. Patch provided by Stefan Eisenwiener.
    [bsc#1171313, vendor-files.tar.bz2]
* Fri Sep 04 2020
  - Put libns into a separate subpackage to avoid file conflicts
    in the libisc subpackage due to different sonums (bsc#1176092).
* Fri Aug 28 2020
  - Require /sbin/start_daemon: both init scripts, the one used in
    systemd context as well as legacy sysv, make use of start_daemon.
* Tue Aug 18 2020
  - Upgrade to version 9.16.6
    Fixes five vilnerabilities:
    5481.   [security]      "update-policy" rules of type "subdomain" were
      incorrectly treated as "zonesub" rules, which allowed
      keys used in "subdomain" rules to update names outside
      of the specified subdomains. The problem was fixed by
      making sure "subdomain" rules are again processed as
      described in the ARM. (CVE-2020-8624) [GL #2055]
    5480.   [security]      When BIND 9 was compiled with native PKCS#11 support, it
      was possible to trigger an assertion failure in code
      determining the number of bits in the PKCS#11 RSA public
      key with a specially crafted packet. (CVE-2020-8623)
      [GL #2037]
    5479.   [security]      named could crash in certain query resolution scenarios
      where QNAME minimization and forwarding were both
      enabled. (CVE-2020-8621) [GL #1997]
    5478.   [security]      It was possible to trigger an assertion failure by
      sending a specially crafted large TCP DNS message.
      (CVE-2020-8620) [GL #1996]
    5476.   [security]      It was possible to trigger an assertion failure when
      verifying the response to a TSIG-signed request.
      (CVE-2020-8622) [GL #2028]
    For the less severe bugs fixed, see the CHANGES file.
    [bsc#1175443, CVE-2020-8624, CVE-2020-8623, CVE-2020-8621,
    CVE-2020-8620, CVE-2020-8622]
* Thu Aug 06 2020
  - Added "/etc/bind.keys" to NAMED_CONF_INCLUDE_FILES in
    /etc/sysconfig/named to suppress warning message re
    missing file.
    [vendor-files.tar.bz2, bsc#1173983]
* Tue Jul 21 2020
  - Upgrade to version bind-9.16.5
    * The "primary" and "secondary" keywords, when used
      as parameters for "check-names", were not
      processed correctly and were being ignored.
    * 'rndc dnstap -roll <value>' did not limit the number of
      saved files to <value>.
    * Add 'rndc dnssec -status' command.
    * Addressed a couple of situations where named could crash
    For the full list, see the CHANGES file in the source RPM.
* Tue Jun 30 2020
  - Changed /var/lib/named to owner root:named and perms rwxrwxr-t
    so that named, being a/the only member of the "named" group
    has full r/w access yet cannot change directories owned by root
    in the case of a compromized named.
    [bsc#1173307, bind-chrootenv.conf]
* Thu Jun 18 2020
  - Upgrade to version bind-9.16.4
    Fixing two security problems:
    * It was possible to trigger an INSIST when determining
      whether a record would fit into a TCP message buffer.
    * It was possible to trigger an INSIST in
      lib/dns/rbtdb.c:new_reference() with a particular zone
      content and query patterns. (CVE-2020-8619)
    Also the following functional changes:
    * Reject DS records at the zone apex when loading
      master files. Log but otherwise ignore attempts to
      add DS records at the zone apex via UPDATE.
    * The default value of "max-stale-ttl" has been changed
      from 1 week to 12 hours.
    * Zone timers are now exported via statistics channel.
      Thanks to Paul Frieden, Verizon Media.
    Added support for idn2 to spec file (Thanks to Holger Bruenjes
    More internal changes see the CHANGES file in the source RPM
    This update obsoletes
    [bsc#1172958, CVE-2020-8618, CVE-2020-8619,
* Fri May 15 2020
  - Upgrade to version bind-9.16.3
    Fixing two security problems:
    * Further limit the number of queries that can be triggered from
      a request.  Root and TLD servers are no longer exempt
      from max-recursion-queries.  Fetches for missing name server
      address records are limited to 4 for any domain. (CVE-2020-8616)
    * Replaying a TSIG BADTIME response as a request could trigger an
      assertion failure. (CVE-2020-8617)
    * Add engine support to OpenSSL EdDSA implementation.
    * Add engine support to OpenSSL ECDSA implementation.
    * Update PKCS#11 EdDSA implementation to PKCS#11 v3.0.
    * Warn about AXFR streams with inconsistent message IDs.
    * Make ISC rwlock implementation the default again.
    For more see CHANGS file in source RPM.
    [CVE-2020-8616, CVE-2020-8617, bsc#1171740, bind-9.16.3.tar.xz]
* Fri May 08 2020
  - bind needs an accurate clock, so wait for the
    to be reached before starting bind.
    [bsc#1170667, bsc#1170713, vendor-files.tar.bz2]
* Sat Mar 21 2020
  - Use sysusers.d to create named user
  - Have only one package creating the user
* Fri Mar 20 2020
  - coreutils are not used in %post, remove Requires.
  - Use systemd_ordering instead of hard requiring systemd
* Fri Mar 20 2020
  - Upgrade to version 9.16.1
    * UDP network ports used for listening can no longer simultaneously
      be used for sending traffic.
    * The system-provided POSIX Threads read-write lock implementation
      is now used by default instead of the native BIND 9 implementation.
    * Fixed re-signing issues with inline zones which resulted in records
      being re-signed late or not at all.
* Sat Feb 22 2020
  - Update download urls
  - Do not enable geoip on old distros, the geoip db was shut down
    so we need to use geoip2 everywhere
* Thu Feb 20 2020
  - Upgrade to version 9.16.0
    Major upgrade, see
    CHANGES file in the source tree.
    Major functional change:
    * What was set with --with-tuning=large option in older BIND9
      versions is now a default, and a --with-tuning=small option was
      added for small (e.g. OpenWRT) systems.
    * A new "dnssec-policy" option has been added to named.conf to
      implement a key and signing policy (KASP) for zones.
    * The command (and manpage) bind9-config have been dropped as the
      BIND 9 libraries are now purely internal.
    No patches became obsolete through the upgrade.
* Wed Jan 08 2020
  - Upgrade to bind-9.14.9
    bug fixes and feature improvements
* Tue Nov 19 2019
  - Upgrade to version 9.14.8:
    * Set a limit on the number of concurrently served pipelined TCP
    * Some other bug fixing, see CHANGES file.
    [CVE-2019-6477, bsc#1157051]
* Fri Nov 08 2019
  - Upgrade to version 9.14.7
    * removed dnsperf, idn, nslint, perftcpdns, query-loc-0.4.0,
      queryperf, sdb, zkt from contrib as they are not supported
      any more
    * Added support for the GeoIP2 API from MaxMind
    * See CHANGES file in the source RPM.
    * obsoletes bind-CVE-2018-5745.patch (bsc#1126068)
    * obsoletes bind-CVE-2019-6465.patch (bsc#1126069)
    * obsoletes bind-CVE-2018-5743.patch (bsc#1133185)
    * obsoletes bind-CVE-2019-6471.patch (bsc#1138687)
    [bsc#1111722, bsc#1156205, bsc#1126068, bsc#1126069, bsc#1133185,
    bsc#1138687, CVE-2019-6476, CVE-2019-6475,
    CVE-2019-6471, CVE-2018-5743, CVE-2019-6467, CVE-2019-6465,
    CVE-2018-5745, CVE-2018-5744, CVE-2018-5740, CVE-2018-5738,
    CVE-2018-5737, CVE-2018-5736, CVE-2017-3145, CVE-2017-3136,, bind-99-libidn.patch, perl-path.diff,
    bind-sdb-ldap.patch, bind-CVE-2017-3145.patch,
    bind-fix-fips.patch, bind-CVE-2018-5745.patch,
    bind-CVE-2019-6465.patch, bind-CVE-2018-5743.patch,
    bind-CVE-2019-6471.patch, CVE-2016-6170, bsc#1018700,
    bsc#1018701, bsc#1018702, bsc#1033466, bsc#1033467, bsc#1033468,
    bsc#1040039, bsc#1047184, bsc#1104129, bsc#906079, bsc#918330,
    bsc#936476, bsc#937028, bsc#939567, bsc#977657, bsc#983505,
    bsc#987866, bsc#989528, fate#320694, fate#324357, bnc#1127583,
    bnc#1127583, bnc#1109160]
* Fri Jul 12 2019
  - removal of SuSEfirewall2 service from Factory, since SuSEfirewall2 has been
    replaced by firewalld, see [1].
* Tue Apr 16 2019
  - Add FIPS patch back into bind (bsc#1128220)
  - File: bind-fix-fips.patch
* Mon Dec 10 2018
  - Don't rely on /etc/insserv.conf anymore for proper dependencies
    against in named.service and lwresd.service
    (bsc#1118367 bsc#1118368)
* Tue Sep 25 2018
  - Update named.root. One of the root servers IP has changed.
  - Install the LICENSE file.
* Fri Jul 06 2018
  - Add bind.conf and bind-chrootenv.conf to install the default
    files in /var/lib/named and create chroot environment on systems
    using transactional-updates [bsc#1100369] [FATE#325524].
* Fri Jun 22 2018
  - Cleanup pre/post install: remove all old code which was needed to
    update to SLES8.
* Wed Jun 06 2018
  - Fix a patch error in dnszone-schema file (bsc#901577)
* Tue Jun 05 2018
  - Add SPF records in dnszone-schema file (bsc#901577)
* Tue Jun 05 2018
  - Fix the hostname in ldapdump to be valid (bsc#965748)
  - Patch file - bind-ldapdump-use-valid-host.patch
* Mon May 21 2018
  - Add bug-4697-Restore-workaround-for-Microsoft-Windows-T.patch
    Fixes dynamic DNS updates against samba and Microsoft DNS servers
* Thu May 17 2018
  - Move chroot related files from bind to bind-chrootenv
* Wed May 16 2018
  - Remove rndc.key generation from bind.spec file because bind
    should create it on first boot (bsc#1092283)
  - Add misisng rndc.key check and generation code is lwresd.init
* Mon Feb 26 2018
  - build with --enable-filter-aaaa to make it possible to use
    config option "filter-aaaa-on-v4 yes". Useful to workaround
    broken websites like netflix which block traffic from certain
    IPv6 tunnel providers. (bsc#1069633)
* Fri Feb 16 2018
  - Add /dev/urandom to chroot env
* Wed Feb 07 2018
  - Implement systemd init scripts for bind and lwresd (fate#323155)
* Tue Jan 23 2018
  - Apply bind-CVE-2017-3145.patch to fix CVE-2017-3145 (bsc#1076118)
* Wed Dec 06 2017
  - Use getent when adding user/group
  - update changelog to mention removed options
* Sat Nov 25 2017
  - license changed to MPL-2.0 according to legal.
* Thu Nov 23 2017
  - Replace references to /var/adm/fillup-templates with new
    %_fillupdir macro (boo#1069468)
* Wed Nov 22 2017
  - Add back init scripts, systemd units aren't ready yet
* Tue Nov 21 2017
  - Add python3-bind subpackage to allow python bind interactions
* Tue Nov 21 2017
  - Sync configure options with RH package and remove unused ones
    * Enable python3
    * Enable gssapi
    * Enable dnssec scripts
    * Remove no longer recognized --enable-rrl
* Tue Nov 21 2017
  - Drop idnkit from the build, the bind uses libidn since 2007 to run
    all the resolutions in dig/etc. bsc#1030306
  - Add patch to make sure we build against system idn:
    * bind-99-libidn.patch
  - Refresh patch:
    * pie_compile.diff
  - Remove patches that are unused due to above:
    * idnkit-powerpc-ltconfig.patch
    * runidn.diff
* Tue Nov 21 2017
  - drop bind-openssl11.patch (merged upstream)
* Fri Nov 17 2017
  - Remove systemd conditionals as we are not building on sle11 anyway
  - Force the systemd to be base for the initscript deployment
* Wed Nov 15 2017
  - Bump up version of most of the libraries
  - Rename the subpackages to match the version updates
  - Add macros for easier handling of the library package names
  - Drop more unneeded patches
    * dns_dynamic_db.patch (upstream)
* Tue Nov 14 2017
  - Update to 9.11.2 release:
    * Many changes compared to 9.10 see the README file for in-depth listing
    * For detailed changes with issues see CHANGES file
    * Fixes for CVE-2017-3141 CVE-2017-3140 CVE-2017-3138 CVE-2017-3137
      CVE-3136 CVE-2016-9778
    * OpenSSL 1.1 support
  - Remove support for some old distributions and cleanup the spec file
    to require only what is really needed
  - Switch to systemd (bsc#1053808)
  - Remove german from the postinst messages
  - Remove patches merged upstream:
    * bind-CVE-2017-3135.patch
    * bind-CVE-2017-3142-and-3143.patch
  - Refresh named.root with another update
* Mon Nov 13 2017
  - Use python3 by default (fate#323526)
* Mon Sep 11 2017
  - bind-openssl11.patch: add a patch for enabling
    openssl 1.1 support (builds for 1.0 and 1.1 openssl).
* Tue Aug 01 2017
  - Enable JSON statistics
* Fri Jul 14 2017
  - named.root: refreshed from internic to 2017060102 (bsc#1048729)
* Mon Jul 03 2017
  - Run systemctl daemon-reload even when this is not build with
    systemd support: if installing bind on a systemd service and not
    reloading systemd daemon, then the service 'named' is not known
    right after package installation, causing confusion.
* Fri Jun 30 2017
  - Added bind-CVE-2017-3142-and-3143.patch to fix a security issue
    where an attacker with the ability to send and receive messages
    to an authoritative DNS server was able to circumvent TSIG
    authentication of AXFR requests. A server that relies solely on
    TSIG keys for protection with no other ACL protection could be
    manipulated into (1) providing an AXFR of a zone to an
    unauthorized recipient and (2) accepting bogus Notify packets.
    [bsc#1046554, CVE-2017-3142, bsc#1046555, CVE-2017-3143]
* Sat May 20 2017
  - Fix named init script to dynamically find the location of the
    openssl engines (boo#1040027).
* Mon Mar 20 2017
  - Add with_systemd define with default off, since we still use init
    scripts and no systemd units.
* Sat Feb 18 2017
  - Don't require and call insserv if we use systemd
* Wed Feb 15 2017
  - Fix assertion failure or a NULL pointer read for configurations using both DNS64 and RPZ
    * CVE-2017-3135, bsc#1024130
    * bind-CVE-2017-3135.patch
* Thu Jan 12 2017
  - Update to latest release in the 9.10.X series
    * Security fixes in 9.10.4
    * Duplicate EDNS COOKIE options in a response could trigger an assertion failure.
      CVE-2016-2088. [RT #41809]
    * The resolver could abort with an assertion failure due to improper DNAME handling
      when parsing fetch reply messages. CVE-2016-1286. [RT #41753]
    * Malformed control messages can trigger assertions in named and rndc.
      CVE-2016-1285. [RT #41666]
    * Certain errors that could be encountered when printing out or logging an OPT record containing
      a CLIENT-SUBNET option could be mishandled, resulting in an assertion failure. CVE-2015-8705. [RT #41397]
    * Specific APL data could trigger an INSIST. CVE-2015-8704. [RT #41396]
    * Incorrect reference counting could result in an INSIST failure if a socket error occurred while performing
      a lookup. CVE-2015-8461. [RT#40945]
    * Insufficient testing when parsing a message allowed records with an incorrect class to be be accepted,
      triggering a REQUIRE failure when those records were subsequently cached. CVE-2015-8000. [RT #40987]
    * For Features and other fixes in 9.10.4 see
    * Description of patch changes
    * BIND 9.10.4-P5 addresses the security issues described in CVE-2016-9131, CVE-2016-9147 and CVE-2016-9444. [bsc#1018699]
    * BIND 9.10.4-P4 addresses the security issue described in CVE-2016-8864.
    * BIND 9.10.4-P3 addresses the security issue described in CVE-2016-2776 and addresses an interoperability issue with ECS clients.
    * BIND 9.10.4-P2 addresses the security issue described in CVE-2016-2775.
    * BIND 9.10.4-P1 addresses Windows installation issues, the %z modifier is not supported under Windows and
      a race condition in the rbt/rbtdb implementation resulting in named exiting due to assertion failures being detected.
    * Following patches removed, fixed upstream
    * cve-2016-2776.patch
    * cve-2016-8864.patch
* Tue Nov 01 2016
  - Apply cve-2016-8864.patch to fix CVE-2016-8864 (bsc#1007829).
* Tue Sep 27 2016
  - Apply cve-2016-2776.patch to fix CVE-2016-2776 (bsc#1000362).
* Thu Jun 16 2016
  - Remove the start/stop dependency of named and lwresd on remote-fs
    to break a service dependency cycle (bsc#947483, bsc#963971).
  - Make /var/lib/named owned by the named user (bsc#908850,
  - Call systemd service macros with the full service name.
* Thu Apr 14 2016
  - remove BuildRequire libcap. That is only a legacy library, not
    actually used for building. libcap-devel pulls in the right one.
* Fri Mar 11 2016
  - Security update 9.10.3-P4:
    * CVE-2016-1285, bsc#970072: assert failure on input parsing can
      cause premature exit.
    * CVE-2016-1286, bsc#970073: An error when parsing signature
      records for DNAME can lead to named exiting due to an assertion
    * CVE-2016-2088, bsc#970074: a deliberately misconstructed packet
      containing multiple cookie options to cause named to terminate
      with an assertion failure.
* Thu Feb 25 2016
  - drop a changing timestamp making build reproducible
* Fri Feb 12 2016
  - Build with --with-randomdev=/dev/urandom otherwise
    libisc will use /dev/random to gather entropy and that might
    block, short read etc..
* Wed Jan 20 2016
  - Security update 9.10.3-P3:
    * Specific APL data could trigger an INSIST (CVE-2015-8704,
    * Certain errors that could be encountered when printing out or
      logging an OPT record containing a CLIENT-SUBNET option could
      be mishandled, resulting in an assertion failure
      (CVE-2015-8705, bsc#962190).
    * Authoritative servers that were marked as bogus (e.g.
      blackholed in configuration or with invalid addresses) were
      being queried anyway.
* Mon Dec 21 2015
  - Update to version 9.10.3-P2 to fix a remote denial of service by
    misparsing incoming responses (CVE-2015-8000, bsc#958861).
* Sun Oct 04 2015
  - Avoid double %setup, it confuses some versions of quilt.
  - Summary/description update
* Tue Sep 22 2015
  - Update to version 9.10.2-P4
    * An incorrect boundary boundary check in the OPENPGPKEY
      rdatatype could trigger an assertion failure.
      (CVE-2015-5986) [RT #40286] (bsc#944107)
    * A buffer accounting error could trigger an
      assertion failure when parsing certain malformed
      DNSSEC keys. (CVE-2015-5722) [RT #40212] (bsc#944066)
* Wed Jul 29 2015
  - Update to version 9.10.2-P3
    Security Fixes
    * A specially crafted query could trigger an assertion failure in message.c.
      This flaw was discovered by Jonathan Foote, and is disclosed in
      CVE-2015-5477. [RT #39795]
    * On servers configured to perform DNSSEC validation, an assertion failure
      could be triggered on answers from a specially configured server.
      This flaw was discovered by Breno Silveira Soares, and is disclosed
      in CVE-2015-4620. [RT #39795]
    Bug Fixes
    * Asynchronous zone loads were not handled correctly when the zone load was
      already in progress; this could trigger a crash in zt.c. [RT #37573]
    * Several bugs have been fixed in the RPZ implementation:
      + Policy zones that did not specifically require recursion could be treated
      as if they did; consequently, setting qname-wait-recurse no; was
      sometimes ineffective. This has been corrected. In most configurations,
      behavioral changes due to this fix will not be noticeable. [RT #39229]
      + The server could crash if policy zones were updated (e.g. via
      rndc reload or an incoming zone transfer) while RPZ processing
      was still ongoing for an active query. [RT #39415]
      + On servers with one or more policy zones configured as slaves, if a
      policy zone updated during regular operation (rather than at startup)
      using a full zone reload, such as via AXFR, a bug could allow the RPZ
      summary data to fall out of sync, potentially leading to an assertion
      failure in rpz.c when further incremental updates were made to the zone,
      such as via IXFR. [RT #39567]
      + The server could match a shorter prefix than what was
      available in CLIENT-IP policy triggers, and so, an unexpected
      action could be taken. This has been corrected. [RT #39481]
      + The server could crash if a reload of an RPZ zone was initiated while
      another reload of the same zone was already in progress. [RT #39649]
* Fri Jul 10 2015
  - Update to version 9.10.2-P2
    - An uninitialized value in validator.c could result in an assertion failure.
      (CVE-2015-4620) [RT #39795]
  - Update to version 9.10.2-P1
    - Include client-ip rules when logging the number of RPZ rules of each type.
      [RT #39670]
    - Addressed further problems with reloading RPZ zones. [RT #39649]
    - Addressed a regression introduced in change #4121. [RT #39611]
    - The server could match a shorter prefix than what was available in
      CLIENT-IP policy triggers, and so, an unexpected action could be taken.
      This has been corrected. [RT #39481]
    - On servers with one or more policy zones configured as slaves, if a policy
      zone updated during regular operation (rather than at startup) using a full
      zone reload, such as via AXFR, a bug could allow the RPZ summary data to
      fall out of sync, potentially leading to an assertion failure in rpz.c when
      further incremental updates were made to the zone, such as via IXFR.
      [RT #39567]
    - A bug in RPZ could cause the server to crash if policy zones were updated
      while recursion was pending for RPZ processing of an active query.
      [RT #39415]
    - Fix a bug in RPZ that could cause some policy zones that did not
      specifically require recursion to be treated as if they did; consequently,
      setting qname-wait-recurse no; was sometimes ineffective. [RT #39229]
    - Asynchronous zone loads were not handled correctly when the zone load was
      already in progress; this could trigger a crash in zt.c. [RT #37573]
    - Fix an out-of-bounds read in RPZ code. If the read succeeded, it doesn't
      result in a bug during operation. If the read failed, named could segfault.
      [RT #38559]
* Wed May 13 2015
  - Fix inappropriate use of /var/lib/named for locating dynamic-DB plugins.
    Dynamic-DB plugins are now loaded from %{_libexecdir}/bind, consistent with
    openSUSE packaging guideline.
  - Install additional header files which are helpful to the development of
    dynamic-DB plugins.
* Fri May 08 2015
  - Depend on systemd macros and sysvinit on post-12.3 only.
  - Create empty lwresd.conf at build time.
  - Reduce file list pre-13.1.
* Fri May 08 2015
  - Update to version 9.10.2
    - Handle timeout in legacy system test. [RT #38573]
    - dns_rdata_freestruct could be called on a uninitialised structure when
      handling a error. [RT #38568]
    - Addressed valgrind warnings. [RT #38549]
    - UDP dispatches could use the wrong pseudorandom
      number generator context. [RT #38578]
    - Fixed several small bugs in automatic trust anchor management, including a
      memory leak and a possible loss of key state information. [RT #38458]
    - 'dnssec-dsfromkey -T 0' failed to add ttl field. [RT #38565]
    - Revoking a managed trust anchor and supplying an untrusted replacement
      could cause named to crash with an assertion failure.
      (CVE-2015-1349) [RT #38344]
    - Fix a leak of query fetchlock. [RT #38454]
    - Fix a leak of pthread_mutexattr_t. [RT #38454]
    - RPZ could send spurious SERVFAILs in response
      to duplicate queries. [RT #38510]
    - CDS and CDNSKEY had the wrong attributes. [RT #38491]
    - adb hash table was not being grown. [RT #38470]
  - Update bind.keyring
  - Update baselibs.conf due to updates to libdns160 and libisc148
* Fri May 08 2015
  - Enable export libraries to support plugin development.
    Install DNSSEC root key.
    Expose new interface for developing dynamic zone database.
    + dns_dynamic_db.patch
* Tue Feb 10 2015
  - PowerPC can build shared libraries for sure.
* Fri Dec 12 2014
  - Explicitly BuildRequire systemd-rpm-macros since it is used
    for lwresd %post etc. Then drop pre-12.x material.
* Thu Dec 11 2014
  - Corrections to baselibs.conf
* Tue Dec 09 2014
  - Update to version 9.10.1-P1
    - A flaw in delegation handling could be exploited to put named into an
      infinite loop.  This has been addressed by placing limits on the number of
      levels of recursion named will allow (default 7), and the number of
      iterative queries that it will send (default 50) before terminating a
      recursive query (CVE-2014-8500); (bnc#908994).
      The recursion depth limit is configured via the "max-recursion-depth"
      option, and the query limit via the "max-recursion-queries" option.
      [RT #37580]
    - When geoip-directory was reconfigured during named run-time, the
      previously loaded GeoIP data could remain, potentially causing wrong ACLs
      to be used or wrong results to be served based on geolocation
      (CVE-2014-8680). [RT #37720]; (bnc#908995).
    - Lookups in GeoIP databases that were not loaded could cause an assertion
      failure (CVE-2014-8680). [RT #37679]; (bnc#908995).
    - The caching of GeoIP lookups did not always handle address families
      correctly, potentially resulting in an assertion failure (CVE-2014-8680).
      [RT #37672]; (bnc#908995).
* Sun Dec 07 2014
  - Convert some hard PreReq to leaner Requires(pre).
  - Typographical and orthographic fixes to description texts.
* Fri Dec 05 2014
  - Fix bashisms in the createNamedConfInclude script.
  - Post scripts: remove '-e' option of 'echo' that may be unsupported
    in some POSIX-compliant shells.
* Fri Dec 05 2014
  - Add openssl engines to the lwresd chroot.
  - Add /etc/lwresd.conf with attribute ghost to the list of files.
  - Add /run/lwresd to the list of files of the lwresd package.
  - Shift /run/named from the chroot sub to the main bind package.
  - Drop /proc from the chroot as multi CPU systems work fine even without it.
* Thu Dec 04 2014
  - Add a versioned dependency when obsoleting packages.
* Thu Dec 04 2014
  - Remove superfluous obsoletes *-64bit in the ifarch ppc64 case; (bnc#437293).
* Wed Dec 03 2014
  - Fix gssapi_krb configure time header detection.
* Sun Nov 30 2014
  - Update root zone (dated Nov 5, 2014).
* Sat Nov 29 2014
  - Update to version 9.10.1
    - This release addresses the security flaws described in CVE-2014-3214 and
  - Update to version 9.10.0
    - DNS Response-rate limiting (DNS RRL), which blunts the impact of
      reflection and amplification attacks, is always compiled in and no longer
      requires a compile-time option to enable it.
    - An experimental "Source Identity Token" (SIT) EDNS option is now available.
    - A new zone file format, "map", stores zone data in a
      format that can be mapped directly into memory, allowing
      significantly faster zone loading.
    - "delv" (domain entity lookup and validation) is a new tool with dig-like
      semantics for looking up DNS data and performing internal DNSSEC
    - Improved EDNS(0) processing for better resolver performance
      and reliability over slow or lossy connections.
    - Substantial improvement in response-policy zone (RPZ) performance.  Up to
      32 response-policy zones can be configured with minimal performance loss.
    - To improve recursive resolver performance, cache records which are still
      being requested by clients can now be automatically refreshed from the
      authoritative server before they expire, reducing or eliminating the time
      window in which no answer is available in the cache.
    - New "rpz-client-ip" triggers and drop policies allowing
      response policies based on the IP address of the client.
    - ACLs can now be specified based on geographic location using the MaxMind
      GeoIP databases.  Use "configure --with-geoip" to enable.
    - Zone data can now be shared between views, allowing multiple views to serve
      the same zones authoritatively without storing multiple copies in memory.
    - New XML schema (version 3) for the statistics channel includes many new
      statistics and uses a flattened XML tree for faster parsing. The older
      schema is now deprecated.
    - A new stylesheet, based on the Google Charts API, displays XML statistics
      in charts and graphs on javascript-enabled browsers.
    - The statistics channel can now provide data in JSON format as well as XML.
    - New stats counters track TCP and UDP queries received
      per zone, and EDNS options received in total.
    - The internal and export versions of the BIND libraries (libisc, libdns,
      etc) have been unified so that external library clients can use the same
      libraries as BIND itself.
    - A new compile-time option, "configure --enable-native-pkcs11", allows BIND
      9 cryptography functions to use the PKCS#11 API natively, so that BIND can
      drive a cryptographic hardware service module (HSM) directly instead of
      using a modified OpenSSL as an intermediary.
    - The new "max-zone-ttl" option enforces maximum TTLs for zones. This can
      simplify the process of rolling DNSSEC keys by guaranteeing that cached
      signatures will have expired within the specified amount of time.
    - "dig +subnet" sends an EDNS CLIENT-SUBNET option when querying.
    - "dig +expire" sends an EDNS EXPIRE option when querying.
    - New "dnssec-coverage" tool to check DNSSEC key coverage for a zone and
      report if a lapse in signing coverage has been inadvertently scheduled.
    - Signing algorithm flexibility and other improvements
      for the "rndc" control channel.
    - "named-checkzone" and "named-compilezone" can now read
      journal files, allowing them to process dynamic zones.
    - Multiple DLZ databases can now be configured.  Individual zones can be
      configured to be served from a specific DLZ database.  DLZ databases now
      serve zones of type "master" and "redirect".
    - "rndc zonestatus" reports information about a specified zone.
    - "named" now listens on IPv6 as well as IPv4 interfaces by default.
    - "named" now preserves the capitalization of names
      when responding to queries.
    - new "dnssec-importkey" command allows the use of offline
      DNSSEC keys with automatic DNSKEY management.
    - New "named-rrchecker" tool to verify the syntactic
      correctness of individual resource records.
    - When re-signing a zone, the new "dnssec-signzone -Q" option drops
      signatures from keys that are still published but are no longer active.
    - "named-checkconf -px" will print the contents of configuration files with
      the shared secrets obscured, making it easier to share configuration (e.g.
      when submitting a bug report) without revealing private information.
    - "rndc scan" causes named to re-scan network interfaces for
      changes in local addresses.
    - On operating systems with support for routing sockets, network interfaces
      are re-scanned automatically whenever they change.
    - "tsig-keygen" is now available as an alternate command
      name to use for "ddns-confgen".
  - Update to version 9.9.6
    New Features
    - Support for CAA record types, as described in RFC 6844 "DNS
      Certification Authority Authorization (CAA) Resource Record",
      was added. [RT#36625] [RT #36737]
    - Disallow "request-ixfr" from being specified in zone statements where it
      is not valid (it is only valid for slave and redirect zones) [RT #36608]
    - Support for CDS and CDNSKEY resource record types was added. For
      details see the proposed Informational Internet-Draft "Automating
      DNSSEC Delegation Trust Maintenance" at
      [RT #36333]
    - Added version printing options to various BIND utilities. [RT #26057]
      [RT #10686]
    - Added a "no-case-compress" ACL, which causes named to use case-insensitive
      compression (disabling change #3645) for specified clients. (This is useful
      when dealing with broken client implementations that use case-sensitive
      name comparisons, rejecting responses that fail to match the capitalization
      of the query that was sent.) [RT #35300]
    Feature Changes
    - Adds RPZ SOA to the additional section of responses to clearly
      indicate the use of RPZ in a manner that is intended to avoid
      causing issues for downstream resolvers and forwarders [RT #36507]
    - rndc now gives distinct error messages when an unqualified zone
      name matches multiple views vs. matching no views [RT #36691]
    - Improves the accuracy of dig's reported round trip times.  [RT #36611]
    - When an SPF record exists in a zone but no equivalent TXT record
      does, a warning will be issued.  The warning for the reverse
      condition is no longer issued. See the check-spf option in the
      documentation for details. [RT #36210]
    - "named" will now log explicitly when using rndc.key to configure
      command channel. [RT #35316]
    - The default setting for the -U option (setting the number of UDP
      listeners per interface) has been adjusted to improve performance.
      [RT #35417]
    - Aging of smoothed round-trip time measurements is now limited
      to no more than once per second, to improve accuracy in selecting
      the best name server. [RT #32909]
    - DNSSEC keys that have been marked active but have no publication
      date are no longer presumed to be publishable. [RT #35063]
    Bug Fixes
    - The Makefile in bin/python was changed to work around a bmake
      bug in FreeBSD 10 and NetBSD 6. [RT #36993] (**)
    - Corrected bugs in the handling of wildcard records by the DNSSEC
      validator: invalid wildcard expansions could be treated as valid
      if signed, and valid wildcard expansions in NSEC3 opt-out ranges
      had the AD bit set incorrectly in responses. [RT #37093] [RT #37072]
    - When resigning, dnssec-signzone was removing all signatures from
      delegation nodes. It now retains DS and (if applicable) NSEC
      signatures.  [RT #36946]
    - The AD flag was being set inappopriately on RPZ responses. [RT #36833]
    - Updates the URI record type to current draft standard,
      draft-faltstrom-uri-08, and allows the value field to be zero
      length [RT #36642] [RT #36737]
    - RRSIG sets that were not loaded in a single transaction at start
      up were not being correctly added to re-signing heaps.  [RT #36302]
    - Setting '-t aaaa' in .digrc had unintended side-effects. [RT #36452]
    - A race condition could cause a crash in isc_event_free during
      shutdown.  [RT #36720]
    - Addresses a race condition issue in dispatch. [RT #36731]
    - acl elements could be miscounted, causing a crash while loading
      a config [RT #36675]
    - Corrects a deadlock between view.c and adb.c. [RT #36341]
    - liblwres wasn't properly handling link-local addresses in
      nameserver clauses in resolv.conf. [RT #36039]
    - Buffers in isc_print_vsnprintf were not properly initialized
      leading to potential overflows when printing out quad values.
      [RT #36505]
    - Don't call qsort() with a null pointer, and disable the GCC 4.9
      "delete null pointer check" optimizer option. This fixes problems
      when using GNU GCC 4.9.0 where its compiler code optimizations
      may cause crashes in BIND. For more information, see the operational
      advisory at [RT #35968]
    - Fixed a bug that could cause repeated resigning of records in
      dynamically signed zones. [RT #35273]
    - Fixed a bug that could cause an assertion failure after forwarding
      was disabled. [RT #35979]
    - Fixed a bug that caused SERVFAILs when using RPZ on a system
      configured as a forwarder. [RT #36060]
    - Worked around a limitation in Solaris's /dev/poll implementation
      that could cause named to fail to start when configured to use
      more sockets than the system could accomodate. [RT #35878]
  - Remove merged rpz2+rl-9.9.5.patch and obsoleted rpz2+rl-9.9.5.patch
  - Removed pid-path.diff patch as /run/{named,lwresd}/ are used by default.
  - Update baselibs.conf (added libirs and library interface version updates).
* Fri Nov 14 2014
  - No longer perform gpg validation; osc source_validator does it
    + Drop gpg-offline BuildRequires.
    + No longer execute gpg_verify.



Generated by rpm2html 1.8.1

Fabrice Bellet, Fri Feb 9 21:17:25 2024