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

Improve handling of nested compression pointers and add columns for multiple answers, authorities and additionals.#19

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

alinari
Copy link

@alinari alinari commented Oct 8, 2014

No description provided.

… returns a comma delimeted list of qname, class and type for each RR in the response. Also adds a qclass LUT.
@alinari alinari changed the title Improve handling of nested compression pointers Improve handling of nested compression pointers and add columns for multiple answers, authorities and additionals. Oct 8, 2014
@jelu jelu mentioned this pull request May 23, 2017
@jelu
Copy link
Member

jelu commented May 23, 2017

@alinari I know it's been a few years but if you can please explain more about 3cc10d4, doesn't the code follow normal DNS name compressed labels?

@candlerb
Copy link

candlerb commented Apr 2, 2018

Add columns answers, authorties, and additionals, each of which which returns a comma delimeted list of qname, class and type for each RR in the response

For multi-valued columns like answers, I wonder if it would be more SQL-like to have a separate pseudo table e.g. dns_answers which you could join onto the dns table. There would need to be some unique key that joins the two (could just be pcap filename + offset)

This would allow you to more easily handle queries like: "show me all queries which resolved to A 1.2.3.4", which is difficult if the answer is a multi-valued, comma-separated list.

@jelu
Copy link
Member

jelu commented Apr 3, 2018

@candlerb Unless you need to do it in SQL, dnsjit will be able to easily do it with a custom Lua filter

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants