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] DNS Lameness Checking Proposal
- Next message (by thread): [dns-wg] DNS Lameness Checking Proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Brett Carr
brettcarr at ripe.net
Tue Aug 8 15:37:13 CEST 2006
As per the dns-wg Action point 52.3 from RIPE 52 "post questions and proposal to wg mailing list on how to deal with lame delegations when either the NCC is responsible for maintaining the parent or for running a (secondary) server for the child that is or is about to become delegated lame due to an unavailable *xfr source." Please find attached "dnslamecheckAug2006.txt" a proposal on how the RIPE NCC should test for lameness and what the resulting actions could be. Your feedback and discussion on this proposal is welcomed. Brett Carr. -- Brett Carr RIPE Network Coordination Centre Systems Engineer -- Operations Group Amsterdam, Netherlands GPG Key fingerprint = F20D B2A7 C91D E370 44CF F244 B6A1 EF48 E743 F7D8 -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: dnslamecheckAug2006.txt URL: </ripe/mail/archives/dns-wg/attachments/20060808/fd7b4acc/attachment.txt>
- Next message (by thread): [dns-wg] DNS Lameness Checking Proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]