On Thu, May 21, 2020 at 6:00 PM Töma Gavrichenkov <xima...@gmail.com> wrote: > > Peace, > > On Thu, May 21, 2020 at 11:08 PM Warren Kumari <war...@kumari.net> wrote: > > [..skip..] > > Looking in the webserver log, there are also some hits - e.g: > > - - [21/May/2020:19:09:10 +0000] "GET /favicon.ico HTTP/1.1" 404 209 > > "http://www.wow4dns.com/"; "Mozilla/5.0 (Macintosh; Intel Mac OS X > > 10_15_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.138 > > Safari/537.36" > > Is there a statistically — or somehow otherwise — reason to think this > was not a coincidence? > (I'm just askin' before going to repeat the same experiment)
Yes, no, maybe?! www.wow4dns.com was never pointed at this machine until I added the glue and NS records (it used to point elsewhere). It's quite probable that this was triggered by something other than the Atlas measurement, but all that that means is that someone actually resolved the name "for real". I haven't seen any more hits since then, so, um, who knows... I initially wanted to do an Atlas HTTP measurement (instead of a DNS measurement), but then realized that the HTTP measurement type can only be directed at a RIPE Anchor (not an arbitrary name). If there are any Atlas folk around (or if people want to test from other tools / vantage points), feel free... W > > -- > Töma -- I don't think the execution is relevant when it was obviously a bad idea in the first place. This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants. ---maf _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
