You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: