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] DNSmon "not indicative of what happens to normal traffic" claims the root ops
- Previous message (by thread): [atlas] DNSmon "not indicative of what happens to normal traffic" claims the root ops
- Next message (by thread): [atlas] DNSmon "not indicative of what happens to normal traffic" claims the root ops
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Chris Amin
camin at ripe.net
Tue Dec 8 16:34:58 CET 2015
On 08/12/2015 16:16, Nico CARTRON wrote: > On 8 December 2015 at 16:07:02, Stephane Bortzmeyer (bortzmeyer at nic.fr > <mailto:bortzmeyer at nic.fr>) wrote: >> http://root-servers.org/news/events-of-20151130.txt > > Thanks Stéphane for your reactivity, as usual :) > > “Such test traffic may not be indicative of what happens to normal > traffic or user experience”. > > Not entirely sure what this means behind, or is it just them trying to > minimise the impact? It could be a bit of expectation management on their part. I agree with the statement that DNSMON and other similar tools do not provide direct insight into end user experience, but that is also not their goal. DNSMON at least is deliberately designed to measure from stable vantage points (RIPE Atlas anchors, formerly TTM boxes), and makes no attempt to simulate how recursive resolvers and end user operating systems may behave. In fact, it avoids such attempts, even to the point that it never retries a failed query, which most clients would do. I would argue that this is a feature of the system, providing as it does a nice clear signal that functions as a good metric for traffic between recursive resolvers and the authoritative servers. For reference, this is what DNSMON "saw" during the reported time period, which seems to correspond to the times in the report: https://atlas.ripe.net/dnsmon/?dnsmon.session.color_range_pls=0-7-7-100-100&dnsmon.session.exclude-errors=true&dnsmon.type=zone-servers&dnsmon.zone=root&dnsmon.startTime=1448798400&dnsmon.endTime=1449021600&dnsmon.ipVersion=both&dnsmon.selectedRows=198.41.0.4,2001:503:ba3e::2:30,192.228.79.201,2001:500:84::b,192.33.4.12,2001:500:2::c,199.7.91.13,2001:500:2d::d,192.203.230.10,192.5.5.241,2001:500:2f::f,192.112.36.4,128.63.2.53,2001:500:1::803f:235,192.36.148.17,2001:7fe::53,192.58.128.30,2001:503:c27::2:30,193.0.14.129,2001:7fd::1,199.7.83.42,2001:500:3::42,202.12.27.33,2001:dc3::35&dnsmon.filterProbes=true&dnsmon.session.color_range_rtt=0-60-60-250-5000&dnsmon.session.color_range_relative-rtt=0-26-26-298-1000 Regards, Chris Amin RIPE NCC Developer -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: </ripe/mail/archives/ripe-atlas/attachments/20151208/57011750/attachment.sig>
- Previous message (by thread): [atlas] DNSmon "not indicative of what happens to normal traffic" claims the root ops
- Next message (by thread): [atlas] DNSmon "not indicative of what happens to normal traffic" claims the root ops
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]