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/ripe-atlas@ripe.net/
[atlas] Fwd: [mat-wg] Atlas: DNS TCP Errors
- Previous message (by thread): [atlas] Fwd: [mat-wg] Atlas: DNS TCP Errors
- Next message (by thread): [atlas] Fwd: [mat-wg] Atlas: DNS TCP Errors
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Tue Mar 14 16:45:15 CET 2017
Hi John, On 2017/03/14 14:49 , John wrote: > feature request, when preforming DNS queries over TCP would it be > possible for the probe to differentiate between a timeout and a TCP > Reset. Currently the result just records the following when it gets a > reset[1]. > > `error.timeout: 5000` I'll create a ticket for that. I have no idea about the ETA at the moment. > A similar feature to record ICMP prohibited for udp queries would also > be useful but likely much harder. I wonder if the retry option would help here. The second send should get an error from the kernel if the previous one resulted in an error ICMP. Actually getting the ICMP is possibly too hard, but a send error may help a bit. But it requires some experimenting to see if this approach would work. Philip
- Previous message (by thread): [atlas] Fwd: [mat-wg] Atlas: DNS TCP Errors
- Next message (by thread): [atlas] Fwd: [mat-wg] Atlas: DNS TCP Errors
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]