<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>My reason for suggesting this was the use of the ripe atlas nodes which would make doing a DNS lookup the easiest one to task these nodes to conduct. </div><div><br></div><div>In other respects (I.e. When asking users) then I agree with you. </div><div><br>Regards<div><br></div><div>Alexander</div><div><br></div><div>Alexander Neilson</div><div>Neilson Productions Ltd</div><div><a href="mailto:Alexander@Neilson.net.nz">Alexander@Neilson.net.nz</a></div><div>021 329 681</div></div><div><br>On 30/03/2014, at 2:20 pm, Colm MacCárthaigh <<a href="mailto:colm@stdlib.net">colm@stdlib.net</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><br><div>You're right, one of the many whoami records would work too, but I usually avoid those for two reasons; 1. users mostly don't know how to make DNS queries and often copy the wrong IP address back in their reports, and 2) the response is cacheable and so unreliable when your resolver has multiple IPs, or if you're testing several resolvers from behind a caching stub resolver. So I wrote the HTTP/Javscript interface with a cache buster to get rid of the problem.</div>
<div><br></div><div>HackerNews user <a href="https://news.ycombinator.com/user?id=erhanerdogan" style="color:rgb(130,130,130);text-decoration:none;font-family:Verdana;font-size:11px;background-color:rgb(246,246,239)">erhanerdogan</a> got back to me with a report: <a href="https://news.ycombinator.com/item?id=7494650">https://news.ycombinator.com/item?id=7494650</a> </div>
<div><br></div><div>Which looks like Google/OpenDNS are being replaced, rather than MITM'd or proxied. But I'd still be interested in more data. </div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Sat, Mar 29, 2014 at 6:08 PM, Alexander Neilson <span dir="ltr"><<a href="mailto:alexander@neilson.net.nz" target="_blank">alexander@neilson.net.nz</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto"><div>Other option here is to do a lookup at <a href="http://whoami.akamai.com" target="_blank">whoami.akamai.com</a> and the DNS result is the IP address they got the DNS request from. <br><br>Regards<div>
<br></div><div>Alexander</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Alexander Neilson</div><div>Neilson Productions Ltd</div><div><a href="mailto:Alexander@Neilson.net.nz" target="_blank">Alexander@Neilson.net.nz</a></div>
<div>021 329 681</div></font></span></div><div><div class="h5"><div><br>On 30/03/2014, at 1:51 pm, Colm MacCárthaigh <<a href="mailto:colm@stdlib.net" target="_blank">colm@stdlib.net</a>> wrote:<br><br></div><blockquote type="cite">
<div><div dir="ltr"><div style="font-family:arial,sans-serif;font-size:13px">Does anyone know if the intercepting recursors are acting as standalone recursive nameservers, or if they are passing on the un-interesting queries to the "real" Google / OpenDNS resolvers? </div>
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">One way to tell is to observe the addresses being used towards authoritative name-servers. <a href="http://whatsmyresolver.stdlib.net/" target="_blank">http://whatsmyresolver.stdlib.net/</a> is one way to see this address. I'd be interested in the results, if anyone is in a position to test. </div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Mar 29, 2014 at 1:46 PM, Stephane Bortzmeyer <span dir="ltr"><<a href="mailto:bortzmeyer@nic.fr" target="_blank">bortzmeyer@nic.fr</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><a href="http://www.bortzmeyer.org/dns-routing-hijack-turkey.html" target="_blank">http://www.bortzmeyer.org/dns-routing-hijack-turkey.html</a><br>
<br>
(with the help of RIPE Atlas probes)<br>
_______________________________________________<br>
dns-operations mailing list<br>
<a href="mailto:dns-operations@lists.dns-oarc.net" target="_blank">dns-operations@lists.dns-oarc.net</a><br>
<a href="https://lists.dns-oarc.net/mailman/listinfo/dns-operationsdns-jobs" target="_blank">https://lists.dns-oarc.net/mailman/listinfo/dns-operations<br>
dns-jobs</a> mailing list<br>
<a href="https://lists.dns-oarc.net/mailman/listinfo/dns-jobs" target="_blank">https://lists.dns-oarc.net/mailman/listinfo/dns-jobs</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Colm
</div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>dns-operations mailing list</span><br><span><a href="mailto:dns-operations@lists.dns-oarc.net" target="_blank">dns-operations@lists.dns-oarc.net</a></span><br>
<span><a href="https://lists.dns-oarc.net/mailman/listinfo/dns-operations" target="_blank">https://lists.dns-oarc.net/mailman/listinfo/dns-operations</a></span><br><span>dns-jobs mailing list</span><br><span><a href="https://lists.dns-oarc.net/mailman/listinfo/dns-jobs" target="_blank">https://lists.dns-oarc.net/mailman/listinfo/dns-jobs</a></span></div>
</blockquote></div></div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Colm
</div>
</div></blockquote></body></html>