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 1854148 - RFE: add DNSTAP to RHEL's 8.x Bind
Summary: RFE: add DNSTAP to RHEL's 8.x Bind
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: bind
Version: 8.0
Hardware: Unspecified
OS: Linux
medium
high
Target Milestone: rc
: 8.0
Assignee: Petr Menšík
QA Contact: Petr Sklenar
Prerana Sharma
URL:
Whiteboard:
Depends On: 1869225
Blocks: 1771008 1845672 1919904 1975268
TreeView+ depends on / blocked
 
Reported: 2020-07-06 14:54 UTC by Kitty
Modified: 2024-10-01 16:41 UTC (History)
10 users (show)

Fixed In Version: bind-9.11.26-2.el8
Doc Type: Enhancement
Doc Text:
.`DNSTAP` now records incoming detailed queries. `DNSTAP` provides an advanced way to monitor and log details of incoming name queries. It also records sent answers from the `named` service. Classic query logging of the named service has a negative impact on the performance of the `named` service. As a result, DNSTAP offers a way to perform continuous logging of detailed incoming queries without impacting the performance penalty. The new `dnstap-read` utility allows you to analyze the queries running on a different system.
Clone Of:
Environment:
Last Closed: 2021-05-18 14:59:05 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Article) 5569091 0 None None None 2020-11-10 22:58:28 UTC
Red Hat Product Errata RHBA-2021:1645 0 None None None 2021-05-18 14:59:31 UTC

Comment 3 Tomáš Hozza 2020-07-09 13:25:45 UTC 
Hello.

Thank you for your request.

I would like to ask about specific reasons (functionality) why the Customer needs DNSTAP in BIND and can not use available tools like wireshark and tcpdump to capture DNS communication and analyze it? 

I would be also interested if there are more customers, who would use this feature, or this is the only single customer that is requesting this functionality? 

What is the business impact on customer if this functionality is not added to RHEL?

Thank you in advance.
Comment 5 Rik Theys 2020-08-04 14:31:44 UTC 
Hi,

(In reply to Tomáš Hozza from comment #3)
> I would like to ask about specific reasons (functionality) why the Customer
> needs DNSTAP in BIND and can not use available tools like wireshark and
> tcpdump to capture DNS communication and analyze it? 

dnstap allows for continuously running performant query logging. Wireshark is fine for ad-hoc investigations, but not for permanently running query logging. Using the default query logging of bind is less performant than dnstap.

> I would be also interested if there are more customers, who would use this
> feature, or this is the only single customer that is requesting this
> functionality? 

I'm not the original reporter of this issue, but we would also like to see this feature implemented.

Regards,
Rik
Comment 9 Petr Menšík 2020-09-23 10:19:18 UTC 
It was enabled also in Fedora by commits [1] and [2]. With required fstrm also available, it would be easy to add it. It would add protobuf-c also to bind-utils. But it does not matter, they are already both in rhel-AppStream

1. https://src.fedoraproject.org/rpms/bind/c/f0b6f15ced5af5f309ccbfe35c6ec38ddca7b619
2. https://src.fedoraproject.org/rpms/bind/c/ae36af4c9fd8189ea9925222f6e9902239f61af3
Comment 47 Christian Bretterhofer 2021-02-18 08:20:24 UTC 
add me to list
Comment 50 errata-xmlrpc 2021-05-18 14:59:05 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 (bind 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/RHBA-2021:1645
Note You need to log in before you can comment on or make changes to this bug.