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] Problems with DNS measurements and NSID
- Previous message (by thread): [atlas] Problems with DNS measurements and NSID
- Next message (by thread): [atlas] Problems with DNS measurements and NSID
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
john
mail at johnbond.org
Wed May 21 00:21:18 CEST 2014
On 20/05/14 19:29, Philip Homburg wrote: > The 'normal' mode for DNS queries is that they get sent to one server. > So you would get one reply each time the measurement is performed. > > The exception is when the measurement is to query the probe's local DNS > resolvers. In that case, up to three resolvers are queried and you can > get as many replies. > > In the past, each replies would be an independent Atlas result. However, > our storage back-end cannot really handle that. So the code was changed > that all three replies are grouped into a single Atlas result. > > Hence, in general, an Atlas DNS result can contain multiple DNS replies. > But only if you select the 'use the probe's local resolvers' option. Thanks for the clarification Philip. good to know.
- Previous message (by thread): [atlas] Problems with DNS measurements and NSID
- Next message (by thread): [atlas] Problems with DNS measurements and NSID
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]