3 ms·

Does dig takes into account time it takes to establish a TCP connection? If it counts only time it takes to send and receive a response (after the connection ha

Does dig takes into account time it takes to establish a TCP connection? If it counts only time it takes to send and receive a response (after the connection has been established) there should be no statistically significant difference in the result.

citrin_ru 4y ago
Looks like dig discounts TCP connect time. In drill I see TCP being 2 times slower than UDP (which is what I would expect) but dig shows approximately the same numbers with and without +tcp.
- SkyLinx 4y ago
  Are you on Mac? What is drill?
  - citrin_ru 4y ago
    drill vs dig comparison was not form mac, but I expect them behave similarly on different platforms. drill is a dig-like utility from NLnet Labs, on Mac can be installed as part of ldns library e. g. using 'brew install ldns'
    - SkyLinx 4y ago
      With Drill I get the same numbers with or without the -t argument for tcp. So it gives a different result from dig. Why?
      - citrin_ru 4y ago
        How these number compare to ping RTT? On FreeBSD I have following numbers - ping: 12ms avg, drill: 13 msec (~RTT), drill -t: 25 msec (2*RTT)
- benmmurphy 4y ago
  if you look at the query in Wireshark from TCP SYN to the DNS response packet was ~11ms for me and dig claimed it was 3ms. kind of surprising that OP found it ALWAYS faster. I had some queries that were faster over UDP. when you are not counting the TCP connection setup I would expect them to be close to the same.