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/[email protected]/
[atlas] Newly-defined traceroute measurement failing with "name resolution failed: non-recoverable failure in name resolution"
- Previous message (by thread): [atlas] Newly-defined traceroute measurement failing with "name resolution failed: non-recoverable failure in name resolution"
- Next message (by thread): [atlas] New Atlas Probe
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Tue Jun 4 23:15:47 CEST 2013
Hi Bill, On 6/4/13 22:27 , Bill Fenner wrote: > > > I picked "Resolve on probe", and used "c.root-servers.net > <http://c.root-servers.net>" as the destination. I'm pretty sure I > didn't make a typo, because I've copy-n-pasted from the dst_name of > the result JSON. > > For reference, the UDM ID is 1010361 and the probes are 4936 and 4938. > Each probe has a working DNS server configured, according to the "My > Probes" view. > > I've no idea what is going on there. It works on other probes and your resolvers also seem to work fine. I'll try to investigate. -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ripe-atlas/attachments/20130604/54d01b82/attachment.html>
- Previous message (by thread): [atlas] Newly-defined traceroute measurement failing with "name resolution failed: non-recoverable failure in name resolution"
- Next message (by thread): [atlas] New Atlas Probe
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]