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 (show unmerged sources)
Filename | Size | Changed |
---|---|---|
bind-9.19.13.tar.xz | 0005430076 5.18 MB | |
bind-9.19.13.tar.xz.asc | 0000000833 833 Bytes | |
bind-ldapdump-use-valid-host.patch | 0000002541 2.48 KB | |
bind.changes | 0000178108 174 KB | |
bind.conf | 0000000444 444 Bytes | |
bind.keyring | 0000009606 9.38 KB | |
bind.spec | 0000021108 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 |
Latest Revision
Jorik Cronenberg (jcronenberg)
committed
(revision 6)
- Update to release 9.19.13 New Features: * dnstap-read can now print long timestamps with millisecond precision. Bug Fixes: * When the same notify-source address and port number was configured for multiple destinations and zones, an unresponsive server could tie up the relevant network socket until it timed out; in the meantime, NOTIFY messages for other servers silently failed. named will now retry sending such NOTIFY messages over TCP. Furthermore, NOTIFY failures are now logged at the INFO level. * The max-transfer-time-in and max-transfer-idle-in have not had any effect since the BIND 9 networking stack was refactored in version 9.16. The missing functionality has been re-implemented and incoming zone transfers now time out properly when not progressing. * The read timeout in rndc is now 60 seconds, matching the behavior in BIND 9.16 and earlier. It had previously been lowered to 30 seconds by mistake. * When the ISC_R_INVALIDPROTO (ENOPROTOOPT, EPROTONOSUPPORT) error code is returned by libuv, it is now treated as a network failure: the server for which that error code is returned gets marked as broken and is not contacted again during a given resolution process. * 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. * A flaw in reworked code responsible for accepting TCP connections has been addressed. This issue could cause a
Comments 0