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 16:56:56 CET 2015
On 2015/12/08 16:45 , Daniel Karrenberg wrote: > Real resolvers > - use caching, > - retry queries, > - can use all authoritative servers for a zone, > - perform recursion, and (again) > - use caching. > > The typical TTL for caching in the root zone is 48 hours. I wonder if in the case of local DNSSEC validating resolvers behind DNSSEC-unware resolvers in CPEs, this model is still valid.
- 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 ]