Bug 1724071
| Summary: | Latest bind (9.9) update now causes zone transfer to always fail. [rhel-7.6.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | RAD team bot copy to z-stream <autobot-eus-copy> |
| Component: | bind | Assignee: | Petr Menšík <pemensik> |
| Status: | CLOSED ERRATA | QA Contact: | qe-baseos-daemons |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 7.6 | CC: | benji.wakely, cadel2010, cbesson, dcortijo, dwoodruf, eric.eisenhart, fkrska, john.horne, mooney, pemensik, psklenar, rcadova, rhbugs, rik.theys, robert.esser, rwahyudi, scott.frazer, tcrider, thozza, uwe.knop, villapla, ysoni |
| Target Milestone: | rc | Keywords: | Regression, ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | bind-9.9.4-74.el7_6.2 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: Previous security fix introduced regression in handling TCP queries. It affected mostly long running TCP sessions.
Consequence: Transfers of larger zones often failed with timeouts, making slaves zones unreliable. Could be fixed by keep-response-order { any; }; option
Fix: Proper fix were used, removing regression on long running connections. At the same time, new option is not ignored.
Result: TCP sessions work correctly with or without keep-response-order option. It can be removed again from configuration.
|
Story Points: | --- |
| Clone Of: | 1720703 | Environment: | |
| Last Closed: | 2019-07-29 15:16:45 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1720703 | ||
| Bug Blocks: | |||
|
Description
RAD team bot copy to z-stream
2019-06-26 08:13:26 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:1899 |