matthewrs_rahl
New member
I've been playing around with the unix terminal "Dig" command trying to figure out how to get it to output total time without success (I'm of the opinion that no such option exists, as it's not listed in the man page - feel free to correct me if I'm wrong though and I will look again). During the process of investigation though I encountered something odd with the "+Stat" flag.
>>>>Take for example a regular dig, e.g. "dig www.google.com"
The result will show you a "Query Time: ## MS" <--- Note "MS" for Milliseconds.
>>>>Now try "dig www.google.com +stats"
The result will show you a "Query Time: ### msec" <----Note "msec" for Milliseconds.
And yet when I use these commands, I REPEATEDLY get a results that are 10x longer for queries run with "+Stats", even though they both report in milliseconds. So, what gives? Is the passing of this command somehow affecting the query (it shouldn't - it ought to just be timing it on the client-side) or were the dig writers being weird when they wrote "ms" for one and "msec" for the other (even though they both mean millisecond)?
>>>>Take for example a regular dig, e.g. "dig www.google.com"
The result will show you a "Query Time: ## MS" <--- Note "MS" for Milliseconds.
>>>>Now try "dig www.google.com +stats"
The result will show you a "Query Time: ### msec" <----Note "msec" for Milliseconds.
And yet when I use these commands, I REPEATEDLY get a results that are 10x longer for queries run with "+Stats", even though they both report in milliseconds. So, what gives? Is the passing of this command somehow affecting the query (it shouldn't - it ought to just be timing it on the client-side) or were the dig writers being weird when they wrote "ms" for one and "msec" for the other (even though they both mean millisecond)?