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 ]
Daniel Karrenberg
daniel.karrenberg at ripe.net
Tue Dec 8 17:08:03 CET 2015
On 8.12.15 16:56 , Philip Homburg wrote: > 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. At the risk of turning this into another DNS discussion list: Why are you wondering exactly? DNSSEC validating resolvers do cache, don't they? Daniel whose CPE runs unbound
- 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 ]