<!DOCTYPE html><html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /></head><body><div data-html-editor-font-wrapper="true" style="font-family: arial, sans-serif; font-size: 13px;">For reference, it still appears on <a rel="external nofollow noopener noreferrer" target="_blank" tabindex="-1" href="https://atlas.ripe.net/">https://atlas.ripe.net/</a> for me -<br><br><img alt="" src="cid:7e511365feaed44dd594db7c282b017a"><br><br>Tom<br><br>May 9, 2017 9:14 AM, <a target="_blank" tabindex="-1" href="mailto:w.b.devries@utwente.nl">w.b.devries@utwente.nl</a> wrote:<br> <blockquote><div><div dir="ltr" style="font-size: 12pt;color: #000000;background-color: #FFFFFF;font-family: Calibri,Arial,Helvetica,sans-serif"> <p>Hi Davey,</p> <p>There used to be a message on the atlas.ripe.net frontpage, I retrieved it from google cache:</p> <p style='box-sizing: border-box;margin-right: 0px;margin-bottom: 12px;margin-left: 0px;color: rgb(51, 51, 51);font-family: "Open Sans", Helvetica, Arial, sans-serif;font-size: 14.3px;background-color: rgb(249, 249, 249)'>Due to an unfortunate bug in a recent probe firmware (version 4760), TCP based DNS measurements are not providing correct results. This affects all ongoing and one-off measurements.</p> <p style='box-sizing: border-box;margin-right: 0px;margin-bottom: 12px;margin-left: 0px;color: rgb(51, 51, 51);font-family: "Open Sans", Helvetica, Arial, sans-serif;font-size: 14.3px;background-color: rgb(249, 249, 249)'>The issue also affected DNSMON measurements between 14-23 March. On 23 March we deployed a corrected firmware on RIPE Atlas anchors (version 4770), and in the near future we'll deploy it on regular probes as well.</p> <p style='box-sizing: border-box;margin-right: 0px;margin-bottom: 12px;margin-left: 0px;color: rgb(51, 51, 51);font-family: "Open Sans", Helvetica, Arial, sans-serif;font-size: 14.3px;background-color: rgb(249, 249, 249)'>Our excuses for the inconvenience caused!</p> <p>So any probe that is still on version 4760 will provide timeouts for TCP DNS lookups.</p> <p>Cheers,</p> <p>Wouter</p> <div style="color: rgb(33, 33, 33)"> <hr tabindex="-1" style="display: inline-block;width: 98%"> <div dir="ltr"> <font face="Calibri, sans-serif" color="#000000" style="font-size: 11pt"><b>From:</b> ripe-atlas <<a target="_blank" rel="noopener noreferrer" href="mailto:ripe-atlas-bounces@ripe.net">ripe-atlas-bounces@ripe.net</a>> on behalf of Davey Song($BAWNS7r(B) <<a target="_blank" rel="noopener noreferrer" href="mailto:ljsong@biigroup.cn">ljsong@biigroup.cn</a>><br><b>Sent:</b> Tuesday, May 9, 2017 10:03 AM<br><b>To:</b> <a target="_blank" rel="noopener noreferrer" href="mailto:ripe-atlas@ripe.net">ripe-atlas@ripe.net</a><br><b>Subject:</b> [atlas] Many timeout-failures for DNS over TCP</font><div></div> </div> <div><div> <p><span lang="EN-US">Hi folks, </span></p> <p><span lang="EN-US">I setup measurements for DNS queries over both TCP and UDP. I found the timeout and failures of TCP is far more than UDP. </span></p> <p><span lang="EN-US">For example :</span></p> <p><span lang="EN-US">DNS over TCP: <a rel="external nofollow noopener noreferrer" target="_blank" tabindex="-1" href="https://atlas.ripe.net/measurements/8552847/#!probes"> https://atlas.ripe.net/measurements/8552847/#!probes</a></span></p> <p><span lang="EN-US">DNS over UDP: <a rel="external nofollow noopener noreferrer" target="_blank" tabindex="-1" href="https://atlas.ripe.net/measurements/8552846/#!probes"> https://atlas.ripe.net/measurements/8552846/#!probes</a> </span></p> <p><span lang="EN-US">Is it normal ? I mean is there any special timeout routine/parameters of atlas probes from normal resolver?</span></p> <p><span lang="EN-US">Best regards,</span></p> <p><span lang="EN-US">Davey</span></p> </div></div> </div> </div></div></blockquote> <br> <signature></signature><br> </div></body></html>