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/dns-wg@ripe.net/
[dns-wg] Turning off lameness checks for reverse
- Previous message (by thread): [dns-wg] Turning off lameness checks for reverse
- Next message (by thread): [dns-wg] Turning off lameness checks for reverse
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Florian Weimer
fweimer at bfk.de
Wed Apr 1 13:16:23 CEST 2009
* Shane Kerr: > Which servers are supposed to be seeing increased traffic? The parent > servers should have exactly the same number of queries. Some recursors will consult the parent again, before the TTL expires, to check if the delegation has changed. This seems to happen when a referral returns only unreachable name servers. (When using DNSSEC, this is also the only way to recover from a spoofed referral.) I'm torn about the current lameness notifications. Even in the current form, they helped us to catch a rather embarrassing error. But I think the notifications should be based on current data, and the they should contain more information (timestamps, types of probes and responses). -- Florian Weimer <fweimer at bfk.de> BFK edv-consulting GmbH http://www.bfk.de/ Kriegsstraße 100 tel: +49-721-96201-1 D-76133 Karlsruhe fax: +49-721-96201-99
- Previous message (by thread): [dns-wg] Turning off lameness checks for reverse
- Next message (by thread): [dns-wg] Turning off lameness checks for reverse
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]