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] querying the config
- Previous message (by thread): [atlas] querying the config
- Next message (by thread): [atlas] querying the config
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Michael Rabinovich
michael.rabinovich at case.edu
Thu Jan 28 17:01:21 CET 2021
Hi Randy, In addition, whether it's the configuration or the IP address used by the probe for a query as Hugo suggested, this would only give you the entry point into the resolution path (and sometimes will be a private IP address of a simple forwarder). But you can query for TXT record for whoami.ds.akahelp.net, which will return you the IP address of the egress resolver. Misha > On Jan 27, 2021, at 4:03 PM, Hugo Salgado <hsalgado at nic.cl> wrote: > > Hi Randy. I don't know if you can check the config, but if you launch > a DNS measurement taking care to define use_probe_resolver:true, then > in the dst_addr field of the results you will have the IP that it used > as the resolver. > > Hugo > > On 12:23 27/01, Randy Bush wrote: >> howdy >> >> so i wanted info about a probe's config, specifically what dns >> resolver(s) it is using. i could not figure out how to do this. >> assuming it was a lack of clueons, i asked a friend with far deeper >> atlas fu. they said such queries are not available. really? >> >> [ yes we have bright ideas on how to discover this indirectly by >> mining past data ] >> >> but really? >> >> randy >>
- Previous message (by thread): [atlas] querying the config
- Next message (by thread): [atlas] querying the config
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]