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] Request to test TCP and UDP to the root servers separately.
- Previous message (by thread): [atlas] Request to test TCP and UDP to the root servers separately.
- Next message (by thread): [atlas] Request to test TCP and UDP to the root servers separately.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Sat Feb 25 22:38:35 CET 2012
On 2/25/12 21:18 , Lars-Johan Liman wrote: > philip.homburg at ripe.net: >> The probes are already measuring this. I don't think we made any >> graphs of the results. > > dig @X.root-servers.net . ANY +dnssec At the moment we don't have EDNS or ANY. That should get added whenever we get around to doing DNSSEC. > ticles the root servers to send a 3966-byte message, which triggers > interesting behaviour in my neck of the woods - such as fragment > reordering and consequential reassembly failure - so it's important to > not only look at the IP result of the query, but to actually look at the > arriving packets. > Why does packet reordering lead to reassembly failures? At the moment we also don't have code for capturing fragments. That may be non-trivial to add.
- Previous message (by thread): [atlas] Request to test TCP and UDP to the root servers separately.
- Next message (by thread): [atlas] Request to test TCP and UDP to the root servers separately.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]