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]/
[members-discuss] Reverse DNS issue - zone still not working fromripe DNS server
- Previous message (by thread): [members-discuss] Reverse DNS issue - zone still not working fromripe DNS server
- Next message (by thread): [members-discuss] Reverse DNS issue - zone still not working fromripe DNS server
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Simon Lockhart
s.lockhart at cablecomnetworking.co.uk
Tue Jun 19 17:26:32 CEST 2012
On Tue Jun 19, 2012 at 04:18:22PM +0100, [Swift Internet] Jarek Grzabel wrote: > I have just read this: > https://labs.ripe.net/Members/dfk/timeline-of-reverse-dns-events > > And I'm shocked. The whole internet relies on the organization which clearly > says: > 14:00 Discovery that backups are not available > > How this is possible ? Often, when data is reproducable, it's not a requirement to backup the data if the original inputs are backed up. All a backup would do is speed up time to recovery, as it's always possible to regenerate the data from input. Yes, in this case speed of recovery was important, and those backups would have helped, but I don't think it's fair to come to the conclusion that RIPE doesn't hold backups. Simon
- Previous message (by thread): [members-discuss] Reverse DNS issue - zone still not working fromripe DNS server
- Next message (by thread): [members-discuss] Reverse DNS issue - zone still not working fromripe DNS server
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]