Skip to content
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

Closed
McStork opened this issue Oct 31, 2015 · 5 comments
Closed

Add EDNS and DNSSEC awareness to DNS protocol plugin #345

McStork opened this issue Oct 31, 2015 · 5 comments

Comments

@McStork
Copy link
Contributor

McStork commented Oct 31, 2015

Hello,
I would like to implement the DNS protocol missing features. I already forked and the TCP part is on its way.

@andrewkroh
Copy link
Member

@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.

@McStork McStork mentioned this issue Nov 19, 2015
@andrewkroh andrewkroh changed the title Implementing DNS over TCP / EDNS / DNSSEC Add EDNS and DNSSEC awareness to DNS protocol plugin Jan 13, 2016
@andrewkroh
Copy link
Member

I am updating the title to reflect the fact that support for monitoring DNS traffic over TCP has been added.

@andrewkroh
Copy link
Member

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

@McStork
Copy link
Contributor Author

McStork commented Mar 9, 2016

@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.

@McStork
Copy link
Contributor Author

McStork commented Apr 20, 2016

#1292 closes this.
The DNS protocol in Packetbeat could still use some work (grep TODO in dns package), but as far as TCP, EDNS and DNSSEC are concerned, it's done with.

@McStork McStork closed this as completed Apr 20, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants