[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 ]
Bruce Campbell
bruce.campbell at ripe.net
Fri Oct 3 09:54:12 CEST 2003
On Thu, 2 Oct 2003, Daniel Roesen wrote: > On Wed, Oct 01, 2003 at 05:39:28PM +0200, Olaf M. Kolkman wrote: > > - 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: > - higher resolution delays as more indirection is involved In abstract terms, this project merely changes the authoritative data source for the DNS-based data (delegations), moving it from the current zone files, to the RIPE Database. No additional DNS indirection is involved or created by this project. ( Note that the NCC currently secondaries /16-level zones on ns.ripe.net when /16-level delegations are requested, thus cutting out one level of indirection when queries hit ns.ripe.net . No change to this behaviour is introduced by this project ) > 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? The end goal is that the authoritative DNS data is taken from the Database, such that barring the lag time (minimal) between a Database update, and publication of the same data in DNS, there are no inconsistencies between the two data sets. Kind regards, -- Bruce Campbell RIPE Systems/Network Engineer NCC www.ripe.net - PGP562C8B1B Operations/Security
- 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 ]