Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
.`stale-answer` now provides old cached records in case of DDoS attack
Previously, the Distributed Denial of Service (DDoS) attack caused the authoritative servers to fail with the SERVFAIL error. With this update, the `stale-answer` functionality provides the expired records until a fresh response is obtained.
To enable or disable the `serve-stale` feature, use either of these:
* Configuration file
* Remote control channel (rndc)
Description of problem:
Support for stale-answer-enable and others is missing. Allows responding from cache when authoritative servers are under attack or not responding.
Upstream change:
4700. [func] Serving of stale answers is now supported. This
allows named to provide stale cached answers when
the authoritative server is under attack.
See max-stale-ttl, stale-answer-enable,
stale-answer-ttl. [RT #44790]
First commit:
https://gitlab.isc.org/isc-projects/bind9/commit/df50751585b64f72d93ad665abf0f485c8941a3b
Check bug #1653111 comment #7 for more details.
Version-Release number of selected component (if applicable):
bind-9.11.4-14.P2.el8
Additional info:
Upstream has no support for stale cache in 9.11 ESV version, the feature was introduced in 9.12 version.
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/RHSA-2020:1845
Description of problem: Support for stale-answer-enable and others is missing. Allows responding from cache when authoritative servers are under attack or not responding. Upstream change: 4700. [func] Serving of stale answers is now supported. This allows named to provide stale cached answers when the authoritative server is under attack. See max-stale-ttl, stale-answer-enable, stale-answer-ttl. [RT #44790] First commit: https://gitlab.isc.org/isc-projects/bind9/commit/df50751585b64f72d93ad665abf0f485c8941a3b Check bug #1653111 comment #7 for more details. Version-Release number of selected component (if applicable): bind-9.11.4-14.P2.el8 Additional info: Upstream has no support for stale cache in 9.11 ESV version, the feature was introduced in 9.12 version.