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] DNSmon "not indicative of what happens to normal traffic" claims the root ops
- Previous message (by thread): [atlas] DNSmon "not indicative of what happens to normal traffic" claims the root ops
- Next message (by thread): [atlas] DNSmon "not indicative of what happens to normal traffic" claims the root ops
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Tue Dec 8 17:15:14 CET 2015
On 2015/12/08 17:08 , Daniel Karrenberg wrote: >> I wonder if in the case of local DNSSEC validating resolvers behind >> DNSSEC-unware resolvers in CPEs, this model is still valid. > > At the risk of turning this into another DNS discussion list: Why are > you wondering exactly? DNSSEC validating resolvers do cache, don't they? To give an example, the ssh client I use is linked with getdns. Getdns will try to fetch RRSIG records, etc. from the local resolver. If that fails, getdns will become a full recursive resolver. When ssh starts, the cache of getdns will be empty. And after DNS resolution whatever is cached will not be used anymore.
- Previous message (by thread): [atlas] DNSmon "not indicative of what happens to normal traffic" claims the root ops
- Next message (by thread): [atlas] DNSmon "not indicative of what happens to normal traffic" claims the root ops
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]