[dns-wg] Reverse checker out-of-sync with RIPE-203
- Previous message (by thread): [dns-wg] Last Warning: Termination of <auto-inaddr at ripe.net>
- Next message (by thread): [dns-wg] Reverse checker out-of-sync with RIPE-203
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andre Oppermann
oppermann at pipeline.ch
Fri Jul 16 15:32:43 CEST 2004
The reverse delegation checker on www.ripe.net seems to be out-of-sync with the recommended values in RIPE-203 (or vice-versa). For example RIPE-203 recommends 3600000 seconds (1000 hours = 5 weeks and something) for the SOA expire value. However if I actually put this into my zone file the checker at http://www.ripe.net/cgi-bin/nph-dc.cgi complains that this is too high and suggests a value between 2-4 weeks. Which is is right? One of these should be changed/corrected to resolve this discrepancy. PS: What are the current actual officially recommended SOA values for revese zones? -- Andre
- Previous message (by thread): [dns-wg] Last Warning: Termination of <auto-inaddr at ripe.net>
- Next message (by thread): [dns-wg] Reverse checker out-of-sync with RIPE-203
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]