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.
DescriptionMasahiro Matsuya
2019-02-19 04:47:56 UTC
Description of problem:
This has already been reported on upstream and fixed.
https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=2882
When one of stub servers gets down, the unbound takes much time to process the DNS query in the stub zone, because it tries the dnssec lameness check which is not required. domain-insecure is set to those domain.
Version-Release number of selected component (if applicable):
RHEL7.6
How reproducible:
Always
Steps to Reproduce:
1. Configure unbound as below.
domain-insecure: "example.com"
verbosity: 5
log-time-ascii: yes
log-queries: yes
log-replies: yes
stub-zone:
name: "example.com"
stub-addr: 192.168.1.207
stub-addr: 192.168.1.211
stub-addr: 192.168.1.213
NOTE: The stub server should be authoritative DNS server, and DNSSEC is not enabled.
2. shutdown one of stub-server
3. see the delay with dig command to query any hostname in "example.com"
And, see the following message in the verbose log.
Feb 13 12:18:20 unbound: [26566:0] debug: dnssec status: expected
Feb 13 12:18:20 unbound: [26566:0] info: query response was DNSSEC LAME
NOTE: To get the message of 'debug' level, need to configure rsyslog. for example:
daemon.* /var/log/daemon.log
Actual results:
When one of the stub servers shut down, the dns query has quite big delay. sometimes it timed out. DNS lameness check is done by unbound.
Expected results:
The dns query can complete without delay even when one of stub servers shut down.
Additional info:
A workaround is using "disable-dnssec-lame-check yes".
But, it disables the check for the all domains, not only stub servers with domain-insecure.
The fix patch is:
https://github.com/NLnetLabs/unbound/commit/52aeaf4924ec3f6689e6aafedbe41473d2bda992
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-2020:1092