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.
- Links to home:jcronenberg:branches:network / bind
- Has a link diff
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout home:jcronenberg/bindv9.19 && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| bind-9.19.12.tar.xz | 0005404244 5.15 MB | |
| bind-9.19.12.tar.xz.asc | 0000000833 833 Bytes | |
| bind-ldapdump-use-valid-host.patch | 0000002541 2.48 KB | |
| bind.changes | 0000175925 172 KB | |
| bind.conf | 0000000444 444 Bytes | |
| bind.keyring | 0000009606 9.38 KB | |
| bind.spec | 0000021069 20.6 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 4 (latest revision is 6)
Jorik Cronenberg (jcronenberg)
committed
(revision 4)
- Update to release 9.19.12
Security Fixes:
* An error in DNS message processing introduced in development
version 9.19.11 could cause BIND and its utilities to crash if
the maximum permissible number of DNS labels were present. This
has been fixed.
Known Issues:
* Loading a large number of zones is significantly slower in BIND
9.19.12 than in the previous development releases due to a new
data structure being used for storing information about the
zones to serve. This slowdown is considered to be a bug and
will be addressed in a future BIND 9.19.x development release.
* A flaw in reworked code responsible for accepting TCP
connections may cause a visible performance drop for TCP
queries on some platforms, notably FreeBSD. This issue will be
fixed in a future BIND 9.19.x development release.
New Features:
* BIND now depends on liburcu, Userspace RCU, for lock-free data
structures.
* The new command-line delv +ns option activates name server
mode, to more accurately reproduce the behavior of named when
resolving a query. In this mode, delv uses an internal
recursive resolver rather than an external server. All messages
sent and received during the resolution and validation process
are logged. This can be used in place of dig +trace.
* A new configuration option, checkds, has been introduced. When
set to yes, it detects parental-agents automatically by
resolving the parent NS records. These name servers are queried
to check the DS RRset during a KSK rollover initiated by
dnssec-policy.
Comments 0