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] 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 ]
Bill Woodcock
woody at pch.net
Thu Oct 24 23:35:58 CEST 2019
> On Oct 24, 2019, at 2:22 PM, Kurt Kayser <kurt_kayser at gmx.de> wrote: > 1. Assumption: There is a ton of negative reverse-DNS replies (no PTR-record/NXDOMAIN) returned from the RIPE NCC rev-DNS-Servers, for all not-yet-delegated address-blocks they are responsible for (also called “lame” delegations ?). > 2. Question: How could this be optimized or at least encouraged to be fixed? Doesn’t negative caching enabled by NSEC3 largely take care of this? At least as far as keeping most of the queries away from the authoritative in-addr servers? -Bill -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: Message signed with OpenPGP URL: </ripe/mail/archives/ncc-services-wg/attachments/20191024/c58044a4/attachment.sig>
- 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 ]