[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
Tue May 20 18:17:05 CEST 2014
Hi Daniel, On 20/05/14 17:47, Daniel Quinn wrote: > On Tue 20 May 2014 17:08:47 CEST, Klaus Darilion wrote: > In some cases, DNS results /can/ contain multiple responses. In an > effort to maintain consistency for all DNS results, we opted to treat > all DNS results as if they contain a list of responses — even if that > list is of only one response. This makes it easier to write scripts that > make use of the object, since you always have a consistent data type in > |parsed_result.responses|. I was actually wondering about this myself. What DNS packet would contain multiple responses, considering that the response object relates to the message(s)[1] and not the individual sections. The RFC doesn't explicitly state that a transaction will only contain one message however I can't think of a situation one would send multiple messages. I suspect it is invalid and suspect or would break some implementations one where to try. Thanks John [1]http://tools.ietf.org/html/rfc1035#section-4
- 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 ]