-
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
Add EDNS and DNSSEC awareness to DNS protocol plugin #345
Comments
@McStork I am happy to hear TCP support is being worked. If you have any questions let us know. Also feel free to open up a pull request for your branch even in incomplete form if you would like to get some early feedback. Regarding EDNS and DNSSEC, I was considering switching from using gopacket to miekg/dns since miekg/dns already has support for these. However I haven't looked to see how easy or difficult it would be to switch. |
I am updating the title to reflect the fact that support for monitoring DNS traffic over TCP has been added. |
So that status here is that Packetbeat now uses miekg/dns for parsing. The work remaining is to update Packetbeat to use the library to get the data from the EDNS and DNSSEC records. @McStork Is that correct? Thanks |
@andrewkroh Correct. FYI my schedule requires it to be implemented in two months at the latest. But I might work on it sooner than that. |
#1292 closes this. |
Hello,
I would like to implement the DNS protocol missing features. I already forked and the TCP part is on its way.
The text was updated successfully, but these errors were encountered: