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]/
[ncc-services-wg] Reverse DNS Restructuring Project
- Previous message (by thread): [ncc-services-wg] Reverse DNS Restructuring Project
- Next message (by thread): [ncc-services-wg] Reverse DNS Restructuring Project
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Roesen
dr at cluenet.de
Thu Oct 2 14:08:34 CEST 2003
On Wed, Oct 01, 2003 at 05:39:28PM +0200, Olaf M. Kolkman wrote: > Below you find a proposal for restructuring of parts of the reverse DNS > services. IMHO, a very good idea. > - Once a delegation at a /16 boundary is made the more specific > /24 domain objects are ignored. Hm. This has to consequences which I can see off-hand: - lesser delegations in the RIPE-operated zone files - higher resolution delays as more indirection is involved Is there something I'm missing? And: you're saying that this is part of a filter between the database and the actual zone file generation. Wouldn't this introduce possible inconsistencies between DNS data and database data? Best regards, Daniel
- Previous message (by thread): [ncc-services-wg] Reverse DNS Restructuring Project
- Next message (by thread): [ncc-services-wg] Reverse DNS Restructuring Project
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]