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/
193.in-addr.arpa procedures V1.3
- Previous message (by thread): 193.in-addr.arpa procedures V1.3
- Next message (by thread): 193.in-addr.arpa procedures V1.3
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marten Terpstra
Marten.Terpstra at ripe.net
Fri Mar 26 14:30:58 CET 1993
bonito at nis.garr.it (Antonio_Blasco Bonito) writes: * > * > * > Folks, * > * > One last go. I think we folded in most of the comments from Blaso and othe * rs. * > We have included the procedures for single class C reverse zones, not via * > block zones. * > * > We are already doing our first trials with block delegations, all seems to * > work fine. Please let's get this document accepted and delegate these bloc * ks. * * Sorry for this late comment, but it has come now to my mind: * I think it would be wise to include recommended values for SOA fields * (refresh, retry, etc). This could save problems to ns.ripe.net * when acting as secondary. What do you think recommended values are ? I know have for everything in 193.in-addr.arpa: @ IN SOA ns.ripe.net. hostmaster.ripe.net. ( 1.20 ; Serial 14400 ; Refresh 4 hours 3600 ; Retry 1 hours 604800 ; Expire 7 days 518400 ; TTL 6 days ) which in my view is reasonable, since these things (just delegations) do not change too often. For the actual class C zones, we have for 45.87.192.in-addr.arpa (RIPE NCC net): @ IN SOA ns.ripe.net. hostmaster.ripe.net. ( 1.4 ; Serial 28800 ; Refresh 8 hours 7200 ; Retry 2 hours 604800 ; Expire 7 days 86400 ; Minimum 1 day ) Are these fine to be recommended ? -Marten
- Previous message (by thread): 193.in-addr.arpa procedures V1.3
- Next message (by thread): 193.in-addr.arpa procedures V1.3
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]