This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[atlas] DNS RTT over TCP: twice as long than UDP?
- Previous message (by thread): [atlas] DNS RTT over TCP: twice as long than UDP?
- Next message (by thread): [atlas] DNS RTT over TCP: twice as long than UDP?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Stephane Bortzmeyer
bortzmeyer at nic.fr
Fri Jul 5 14:59:08 CEST 2019
On Fri, Jul 05, 2019 at 12:33:25PM +0000, Giovane Moura <giovane.moura at sidn.nl> wrote a message of 26 lines which said: > My hypothesis is that the field *rtt* on DNS queries on Atlas[1], > for TCP, is, in fact, measuring 2 RTTs: the RTT of the TCP > handshake, and the RTT of query/response itself. I assume (I didn't check with tcpdump) that Atlas starts the clock when the SYN packet leaves, and dig when the DNS request leaves. That would explain your observation. Both make sense, and I disagree when you say that the second method is the only right one. In practice, which method is the most relevant depends on whether you use persistent TCP connections or not.
- Previous message (by thread): [atlas] DNS RTT over TCP: twice as long than UDP?
- Next message (by thread): [atlas] DNS RTT over TCP: twice as long than UDP?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]