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/[email protected]/
[dns-wg] Analysis of NSD
- Previous message (by thread): [dns-wg] Analysis of NSD
- Next message (by thread): [dns-wg] Analysis of NSD
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Koch
pk at TechFak.Uni-Bielefeld.DE
Thu Oct 28 10:45:49 CEST 2004
Jay Daley <td at nominet.org.uk>: > As it happens we use probing not NOTIFY since it gives a greater level of > control over the number of secondaries being updated at once (and the NOTIFY already specifies precautions against a 'rush', although implementations may differ and depending on the size of the zone 'at once' may have different meanings. > bandwidth) and the order in which they are updated. This does rely on > strict calculations of the timings of changes and probes but that is > fairly easy to do. How about sending the NOTIFY messages out of band instead of relying upon retry (and not refresh?)? There's a little 'DoS' potential, though. -Peter
- Previous message (by thread): [dns-wg] Analysis of NSD
- Next message (by thread): [dns-wg] Analysis of NSD
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]