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/db-wg@ripe.net/
Blocks in 193.in-addr.arpa domain document
- Previous message (by thread): Blocks in 193.in-addr.arpa domain document
- Next message (by thread): 193.in-addr.arpa procedures V1.3
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Karrenberg
Daniel.Karrenberg at ripe.net
Wed Mar 24 13:32:25 CET 1993
> Marten Terpstra <Marten.Terpstra at ripe.net> writes: > * Suppose you get: > * inetnum: 193.204.64.0 - 193.204.67.0 > * <administrativia> > * rev-srv: <server1> > * rev-srv: <server2> > * But server1 and server2 only have data for 64.204.193.in-addr.arpa. beca > use > * the remaining three nets in the block are not yet active. > * What will you do? > > My gut feeling would be we add them anyway. If the nets are not yet active, > there is probably no need to do reverse lookups anyway, so noone would > notice. On the other hand this would clash with the constraint that we woul > d > like to see all servers working before we add them ... I think we can put > some intelligence in the rev-srv field to DNS record generator to get aroun > d > these things. Daniel ? We could but the standard answer of course is: Multiple networks can only be folded into one RIPE DB object if all their attributes are the same. So either the reverse servers are up, or there need to be two objects: 193.204.64 and 192.204.65 - 192.204.67. Daniel
- Previous message (by thread): Blocks in 193.in-addr.arpa domain document
- Next message (by thread): 193.in-addr.arpa procedures V1.3
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]