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.
-
1
derived packages
- Links to network / bind
- Has a link diff
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout home:jcronenberg:branches:network/bind && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| bind-9.18.18.tar.xz | 0005490428 5.24 MB | |
| bind-9.18.18.tar.xz.asc | 0000000833 833 Bytes | |
| bind-ldapdump-use-valid-host.patch | 0000002541 2.48 KB | |
| bind.changes | 0000189752 185 KB | |
| bind.conf | 0000000444 444 Bytes | |
| bind.keyring | 0000009606 9.38 KB | |
| bind.spec | 0000021764 21.3 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 | 0000020221 19.7 KB |
Revision 33 (latest revision is 40)
Jorik Cronenberg (jcronenberg)
committed
(revision 33)
- Update to release 9.18.18
Feature Changes:
* When a primary server for a zone responds to an SOA query, but
the subsequent TCP connection required to transfer the zone is
refused, that server is marked as temporarily unreachable. This
now also happens if the TCP connection attempt times out,
preventing too many zones from queuing up on an unreachable
server and allowing the refresh process to move on to the next
configured primary more quickly.
* The dialup and heartbeat-interval options have been deprecated
and will be removed in a future BIND 9 release.
Bug Fixes:
* Processing already-queued queries received over TCP could cause
an assertion failure, when the server was reconfigured at the
same time or the cache was being flushed. This has been fixed.
* Setting dnssec-policy to insecure prevented zones containing
resource records with a TTL value larger than 86400 seconds (1
day) from being loaded. This has been fixed by ignoring the TTL
values in the zone and using a value of 604800 seconds (1 week)
as the maximum zone TTL in key rollover timing calculations.
Comments 0