-
Notifications
You must be signed in to change notification settings - Fork 374
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 to roadmap - AXFR & IXFR #16
Comments
To do this, I will need pcap of the above mentioned traffic. |
http://pcapr.net/browse?q=AXFR On Sat, Feb 25, 2012 at 20:01, Edward Fjellskål
|
Thanks, now I just have to remember my pcapr login :) |
./passivedns -X46CDNPRSOn -l - -r DNS-AXFR.pcap I cant see that there is something to do here. The Answer says its AXFR, but that really dont contain any usefull data, so I skip that. But its the other data in the DNS payload that holds the interesting information, like in that AXFR pcap, it holds the SOA and NS, which we catch with the "O" and "n" flag. Is there something more I should look into here you think ? |
Yeah, but what about a line mentioning that there is an AFXR/IXFR ? On Mon, Feb 27, 2012 at 14:36, Edward Fjellskål
|
Different format it needs, yes. So, We are looking at the answers from the servers, we could do something like: Where the last field could be additional information, that it was an anser to an AFXR. But that said, on the roadmap, I would like to implement a way so that the user can control all the output. Which would be our current format. Additional fields could be to output
|
Add AXFR & IXFR RR types
The text was updated successfully, but these errors were encountered: