-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support receiving dnstap binary logs #12820
Comments
Is Filebeat the right place for this? I thought Filebeat was only for plain-text(-ish) formats, not pure binary formats like dnstap. Should it be its own separate Beat? Large portions of the code could be lifted from the DNS protocol parser in Packetbeat. That seems to all be private functions. Should it be refactored into a supporting library that can be used by both Packetbeat and a "Dnstapbeat"? Keeping the format as similar as possible to the output of Packetbeat seems worthwhile. |
I'm looking for this dnstap integration to the elastic-agent. Is there any progress on this? |
Hi! We're labeling this issue as |
This issue doesn't have a |
Dnstap is definitely still wanted. |
Hi! We're labeling this issue as |
Dnstap stays actual! |
Hi! We're labeling this issue as |
dnstap is binary log format that DNS servers support that records DNS requests and responses. This would allow Beats to receive DNS data directly from the DNS server rather than trying to get the information from packet capture. dnstap is supported by Bind, CoreDNS, Unbound, and more.
With new protocols like DNS-over-TLS (DoT) and DNS-over-HTTP (DoH) being deployed
dnstap
can be a necessary monitoring point for traffic that NSMs would otherwise not have visibility to.An example deployment for an organization might be to have an internal DNS server providing UDP/TCP/DoT/DoH and blocking any DNS traffic (53/udp, 53/tcp, 853/tcp) direct to the internet. With dnstap being enabled, the server it would then let us monitor both the forwarded traffic from the server as well as all the traffic to/from clients.
I'm imagining a dnstap input type for Filebeat.
The text was updated successfully, but these errors were encountered: