[atlas] Trying to measure Quad9 latency

Hi!

Thank you for the pointers Stephane and Baptiste! Already running new
measures!

Best regards,
Eduardo Duarte
Gestão e Desenvolvimento de Projetos l Project Development Management
 
*DNS.PT*
Rua Latino Coelho, n.º 13, 5.º piso | 1050-132 Lisboa | Portugal
Tel: (+351) 211 308 200  Fax: (+351) 211 312 720
dns.pt <http://www.dns.pt> | dnssec.pt <http://www.dnssec.pt> | 3em1.pt
<https://www.3em1.pt> | facebook.com/dns.pt
<https://www.facebook.com/dns.pt> | pt.linkedin.com/in/dnspt
<http://pt.linkedin.com/in/dnspt>

 
Aviso de Confidencialidade/Disclaimer:
Este e-mail foi escrito de acordo com o novo acordo ortográfico.
Esta mensagem é exclusivamente destinada ao seu destinatário, podendo
conter informação CONFIDENCIAL, cuja divulgação está expressamente
vedada nos termos da lei. Caso tenha recepcionado indevidamente esta
mensagem, solicitamos-lhe que nos comunique esse mesmo facto por esta
via devendo apagar o seu conteúdo de imediato. This message is intended
exclusively for its addressee. It may contain CONFIDENTIAL information
protected by law. If this message has been received by error, please
notify us via e-mail and delete it immediately.
[ Antes de imprimir esta mensagem pense no ambiente. Before printing
this message, think about environment ]
Baptiste Jonglez wrote on 22-11-2017 23:14:
> Hi,
>
> On 22-11-17, Eduardo Duarte wrote:
>> Hi all,
>>
>> After the recent launch of the Quad9 service I try to discover if it had
>> a best response time them my actual resolver, that is google public DNS.
>>
>> To do this I launch a comparing measurement using atlas that would run
>> during one day to the same address from the probes in my ISP.
>> The address that I was trying has a very high TTL so I was expecting to
>> always hit the cache of the servers and them get a good comparison base.
>> I know that there are other factors involve in server response time but
>> to my home connection I fill that this where enough.
> Instead of asking for a regular name, you can query a special name like
> "version.bind" in the CHAOS class.  These queries are always answered
> directly, so it simulates a 100% cache hit and allows you to measure the
> RTT towards a resolver.
>
> To test with dig:
>
>   $ dig @9.9.9.9 CH version.bind TXT
>
> See https://atlas.ripe.net/measurements/9740262/ for a real measurement
> using this technique.
>
> Baptiste
>
>> When I got the results from the measurement they were not what I
>> expected.... The measurements to Quad9 had high value of REFUSAL.
>>
>> Does any one as a clue why???
>>
>> The measurement result is available at
>> https://atlas.ripe.net/measurements/10269508
>>
>> Best regards,
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/ripe-atlas/attachments/20171122/ef2a5625/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: </ripe/mail/archives/ripe-atlas/attachments/20171122/ef2a5625/attachment.sig>