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] Feature Request to consider: DNS response IP header
- Previous message (by thread): [atlas] Feature Request to consider: DNS response IP header
- Next message (by thread): [atlas] Feature Request to consider: DNS response IP header
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ponikierski, Grzegorz
gponikie at akamai.com
Thu May 30 15:22:48 CEST 2019
Can be useful to estimate proximity between probe and DNS and to detect nasty middle boxes. To limit overhead on Atlas side, IP header can be provided as raw data to decode on end-user side. Regards, Grzegorz From: Jen Linkova <furry13 at gmail.com> Date: Monday 2019-05-20 at 19:08 To: "ripe-atlas at ripe.net" <ripe-atlas at ripe.net> Subject: [atlas] Feature Request to consider: DNS response IP header Hello, I have a number of use cases when it would be very useful to have access to the IP header of the measurement response packets. In my scenario I'd like to see TTL/Hop Limit of packets received in DNS measurements. So I'm curious if anyone else think it would be a useful feature and if there is some demand for such a feature - maybe the Atlas team could consider implementing it? Thanks! -- SY, Jen Linkova aka Furry -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ripe-atlas/attachments/20190530/15b6f8d8/attachment.html>
- Previous message (by thread): [atlas] Feature Request to consider: DNS response IP header
- Next message (by thread): [atlas] Feature Request to consider: DNS response IP header
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]