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] DNS and recursion
- Previous message (by thread): [atlas] DNS and recursion
- Next message (by thread): [atlas] DNS measurement
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Stephane Bortzmeyer
bortzmeyer at nic.fr
Sat May 27 07:16:38 CEST 2017
On Mon, May 22, 2017 at 02:15:54PM +0200, Chris Amin <camin at ripe.net> wrote a message of 89 lines which said: > This behaviour is still > documented in the manual: > https://atlas.ripe.net/docs/api/v2/manual/measurements/types/type_specific_attributes.html OK, I see, there was a problem in my tests, sorry. Indeed, if I set use_probe_resolver to false, *and* set_rd_bit to false, I get no recursion: 17:10:25.438994 IP (tos 0x0, ttl 64, id 16851, offset 0, flags [DF], proto UDP (17), length 79) 192.168.2.8.58886 > 80.67.169.12.53: [udp sum ok] 13066 A? hdsfdfsqgsqdfysq.bernardtapie.com. (51) (Measurement #8772374) If use_probe_resolver is true, I always have recursion enabled, set_rd_bit is indeed silently ignored. (Something that could be documented in <https://atlas.ripe.net/docs/api/v2/reference/#!/measurements/Measurement_List_GET>)
- Previous message (by thread): [atlas] DNS and recursion
- Next message (by thread): [atlas] DNS measurement
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]