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.
Bug 1664863 - [RFE] named: stale-answer support
Summary: [RFE] named: stale-answer support
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: bind
Version: 8.1
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 8.1
Assignee: Petr Menšík
QA Contact: Robin Hack
Katerina Nemcova
Depends On:
Blocks: 1743192 1755139 1769869
TreeView+ depends on / blocked
Reported: 2019-01-09 21:16 UTC by Petr Menšík
Modified: 2023-09-07 19:38 UTC (History)
7 users (show)

Fixed In Version: bind-9.11.12-3.el8
Doc Type: Enhancement
Doc Text:
.`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)
Clone Of:
: 1769869 (view as bug list)
Last Closed: 2020-04-28 16:52:27 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-25359 0 None None None 2022-01-18 17:39:08 UTC
Red Hat Product Errata RHSA-2020:1845 0 None None None 2020-04-28 16:53:01 UTC

Description Petr Menšík 2019-01-09 21:16:54 UTC
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:

Check bug #1653111 comment #7 for more details.

Version-Release number of selected component (if applicable):

Additional info:
Upstream has no support for stale cache in 9.11 ESV version, the feature was introduced in 9.12 version.

Comment 1 Petr Menšík 2019-01-09 21:30:32 UTC
Note: Serve-stale feature introduced also some defects fixed in 9.12.2-P1 release. It has to be included right away.


Comment 2 Petr Menšík 2019-08-29 09:40:50 UTC
Previous refractoring of resolver [1] makes backport hard. Not simple to check it is possible or not, have to decipher which changes would land where in the old code.

1. https://gitlab.isc.org/isc-projects/bind9/commit/96912e44b0b180de56f47d438f91c9e70925bd16

Comment 3 Petr Menšík 2019-08-29 19:30:58 UTC
Some working prototype was successful. More changes is required, but it seems possible into 9.11.

Comment 18 errata-xmlrpc 2020-04-28 16:52:27 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.


Note You need to log in before you can comment on or make changes to this bug.