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]/
[dns-wg] AAAA lookup misbehaviour
- Previous message (by thread): [dns-wg] AAAA lookup misbehaviour
- Next message (by thread): [dns-wg] draft minutes from RIPE 48 DNS WG sessions
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
David Malone
dwmalone at maths.tcd.ie
Wed Jul 7 15:20:15 CEST 2004
> A more detailed picture would be helpful, including kind of fingerprinting > of the affected systems, so the vendors could be approached directly. I do have some fingerprinting results, but they were a very simple-minded application of fpdns. I'm sure the fpdns authors could do a much better job (in fact, asking for unknown or rare types is probably a useful fingerprinting technqiue). The WG cooperating with the vendors/operators would also be good, as they can then be a part of RIPE efforts to encourage/smooth IPv6 deployment. I'd certainly be interested to see a case study from a (certain) big operator describing the deployment of a fix. OTOH, it may be sufficient to document the problem so it can be more easily diagnosed and fixed by vendors and operators who trip over it. (I presume DNSSEC may run into similar problems with weird responses for unknown types, but I am rather ignorant of the details of DNSSEC.) David.
- Previous message (by thread): [dns-wg] AAAA lookup misbehaviour
- Next message (by thread): [dns-wg] draft minutes from RIPE 48 DNS WG sessions
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]