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 ]
Daniel Karrenberg
daniel.karrenberg at ripe.net
Tue Dec 8 16:54:29 CET 2015
On 8.12.15 16:45 , Nico CARTRON wrote: > > Fully agreed, but I still don’t see why they are downplaying the event > like this. I would call it "putting into perspective". The DNS kept working. > > Tools such as DNSMON are useful, and of course need to be taken with a > grain of salt and not blindly believed “as it”. Again: dnsmon is *not* a tool to measure DNS service. You know that, I know that and most people on this list know that. Most of the people reading a public statement probably *do not* know that. So it needs to be pointed out. Otherwise we will get headlines of doom for no good reason. > > A lot of users/eyeballs have noticed problems, so pretending this did > not happen is not really… constructive. Provide data please! > (OK, they did not pretend this did not happen, but downplaying is kind > of the same to me). See above. Daniel one of "them"
- 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 ]