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/ncc-services-wg@ripe.net/
[ncc-services-wg] Proposal: optimized rev-DNS operations
- Previous message (by thread): [ncc-services-wg] Proposal: optimized rev-DNS operations
- Next message (by thread): [ncc-services-wg] Proposal: optimized rev-DNS operations
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Kurt Kayser
kurt_kayser at gmx.de
Fri Oct 25 14:39:00 CEST 2019
Nick, very simple: Since the IPv6-blocks are quite large, one member might be interested towards areas that have active reverse requests coming in (but those are only visible up to the RIPE NCC servers, if they are not delegated for *all* IPv6 address space, which I doubt will ever happen. If they would have a means to know those top-areas they could (optionally) start analyzing and a delegation process and deliver answers for such addresses. Regards, Kurt Am 25.10.2019 um 11:25 schrieb Nick Hilliard (Network Ability Ltd): > Jim Reid wrote on 25/10/2019 00:19: >> First you need to define the problem you think needs to be fixed. >> Then what you mean by optimise. Neither of these things are clear. > > it's not completely clear that there is a problem here. If people > don't want to set up reverse DNS for their IP address allocations, > then is it really the responsibility of the RIPE NCC to pester them > about this? > > Nick >
- Previous message (by thread): [ncc-services-wg] Proposal: optimized rev-DNS operations
- Next message (by thread): [ncc-services-wg] Proposal: optimized rev-DNS operations
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]