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

Please add reply-log #2676

Open
raatti opened this issue Aug 6, 2015 · 1 comment
Open

Please add reply-log #2676

raatti opened this issue Aug 6, 2015 · 1 comment

Comments

@raatti
Copy link

raatti commented Aug 6, 2015

Many times pdns-logs don't really help quickly in debugging and require tcpdump and other traffic analysis tools to debug simple problems:

Remote x.x.x.x wants 'www.foo.bar|A', do = 0, bufsize = 512: packetcache HIT

This tells that client will get the info from packetcache, yet it doesn't show what is replied to client.
My suggestion: add reply-log to log something like:

Replied to remote x.x.x.x: 'www.foo.bar|A|127.0.0.1'

this way its easier and much faster to see what client asked for and what is the reply it receives.
This also helps to see if one client is receiving too much (large?) replies.

@pieterlexis pieterlexis added this to the rec-4.1.0 milestone Dec 15, 2015
@ahupowerdns ahupowerdns removed this from the rec-4.1.0 milestone Feb 21, 2017
@ahupowerdns ahupowerdns added auth and removed rec labels Feb 21, 2017
@Habbie
Copy link
Member

Habbie commented Mar 7, 2017

We have protobuf logging in rec and dnsdist now. If somebody does protobuf support for auth, this usecase is covered, right?

@Habbie Habbie added this to the auth-helpneeded milestone Mar 7, 2017
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

4 participants