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] interfaces to ripe ncc services (was: Reverse DNS Restructuring Project)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Joerg Schumacher
schuma at gaertner.de
Tue Oct 7 04:26:34 CEST 2003
In article <20031006121932.A4658 at iprg.nokia.com>, David Kessens <david at iprg.nokia.com> wrote: > [...] > For example, simply using the 'rev-srv:' attributes and retiring the > 'domain:' objects seems a lot easier for the user. [...] The RIPE NCC delegates reverse domains on /24 and /16 boundaries only so they don't match inetnum objects very well. The 'rev-srv' might seem to be easier, but thats only true for /16 allocs. rev-srv on e.g. a /29 are meaningless and should go away. Same holds true for a rev-srv on a /24 within a /16. Regards, Joerg
- Previous message (by thread): [ncc-services-wg] Reverse DNS Restructuring Project
- Next message (by thread): [ncc-services-wg] interfaces to ripe ncc services (was: Reverse DNS Restructuring Project)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]