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.
.`unbound` configuration now provides enhanced logging output
With this enhancement, the following three options have been added to the `unbound` configuration:
* `log-servfail` enables log lines that explain the reason for the `SERVFAIL` error code to clients.
* `log-local-actions` enables logging of all local zone actions.
* `log-tag-queryreply` enables tagging of log queries and log replies in the log file.
DescriptionApurbita Mukherjee
2020-06-24 11:16:13 UTC
Description of problem:
To provide additional more logging capability in unbound package in RHEL8
1.7.3 is a 2018 release they are all the way up to 1.10
There are new options in there that may be helpful for logging and DNS security.
# Prints the word 'query' and 'reply' with log-queries and
# log-replies. This makes filtering logs easier. The default is
# off
log-tag-queryreply: yes
# Print log lines to inform about local zone actions.
log-local-actions: yes
# Print log lines that say why queries return SERVFAIL to clients.
log-servfail: yes
Version-Release number of selected component (if applicable):
Unbound 1.7.3
How reproducible:
Always
Steps to Reproduce:
1. If querying the host
host -v example.com 10.xxx.xxx.x
2. The response/answer are not being logged in the log file.
Actual results:
The response/answer are not being logged in the log file.
Expected results:
Answer section to be logged in log file.
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 (Moderate: unbound security, bug fix, and enhancement update), 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-2021:1853
Description of problem: To provide additional more logging capability in unbound package in RHEL8 1.7.3 is a 2018 release they are all the way up to 1.10 There are new options in there that may be helpful for logging and DNS security. # Prints the word 'query' and 'reply' with log-queries and # log-replies. This makes filtering logs easier. The default is # off log-tag-queryreply: yes # Print log lines to inform about local zone actions. log-local-actions: yes # Print log lines that say why queries return SERVFAIL to clients. log-servfail: yes Version-Release number of selected component (if applicable): Unbound 1.7.3 How reproducible: Always Steps to Reproduce: 1. If querying the host host -v example.com 10.xxx.xxx.x 2. The response/answer are not being logged in the log file. Actual results: The response/answer are not being logged in the log file. Expected results: Answer section to be logged in log file.