bind

Edit Package bind

Berkeley Internet Name Domain (BIND) is an implementation of the Domain Name
System (DNS) protocols and provides an openly redistributable reference
implementation of the major components of the Domain Name System.

Refresh
Refresh
Source Files
Filename Size Changed
bind-9.18.10.tar.xz 0005261572 5.02 MB
bind-9.18.10.tar.xz.sha512.asc 0000000874 874 Bytes
bind-ldapdump-use-valid-host.patch 0000002541 2.48 KB
bind.changes 0000174845 171 KB
bind.conf 0000000444 444 Bytes
bind.keyring 0000003966 3.87 KB
bind.spec 0000021418 20.9 KB
dlz-schema.txt 0000006292 6.14 KB
dnszone-schema.txt 0000005637 5.5 KB
named.conf 0000000090 90 Bytes
named.root 0000003310 3.23 KB
vendor-files.tar.bz2 0000020269 19.8 KB
Revision 365 (latest revision is 388)
Jorik Cronenberg's avatar Jorik Cronenberg (jcronenberg) committed (revision 365)
- Update to release 9.18.10
  Feature Changes:
  * To reduce unnecessary memory consumption in the cache, NXDOMAIN
    records are no longer retained past the normal negative cache
    TTL, even if stale-cache-enable is set to yes.
  * The auto-dnssec option has been deprecated and will be removed
    in a future BIND 9.19.x release. Please migrate to
    dnssec-policy.
  * The coresize, datasize, files, and stacksize options have been
    deprecated. The limits these options set should be enforced
    externally, either by manual configuration (e.g. using ulimit)
    or via the process supervisor (e.g. systemd).
  * Setting alternate local addresses for inbound zone transfers
    has been deprecated. The relevant options (alt-transfer-source,
    alt-transfer-source-v6, and use-alt-transfer-source) will be
    removed in a future BIND 9.19.x release.
  * The number of HTTP headers allowed in requests sent to named’s
    statistics channel has been increased from 10 to 100, to
    accommodate some browsers that send more than 10 headers by
    default.
  Bug Fixes:
  * named could crash due to an assertion failure when an HTTP
    connection to the statistics channel was closed prematurely
    (due to a connection error, shutdown, etc.).
  * When a catalog zone was removed from the configuration, in some
    cases a dangling pointer could cause the named process to
    crash.
  * 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
Comments 0
openSUSE Build Service is sponsored by