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]/
[dns-wg] use of "rev-srv" attribute in "inetnum" (and "inet6num") objects
- Previous message (by thread): [dns-wg] use of "rev-srv" attribute in "inetnum" (and "inet6num") objects
- Next message (by thread): [dns-wg] use of "rev-srv" attribute in "inetnum" (and "inet6num") objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
s.steffann at computel.nl
Wed Apr 4 23:27:13 CEST 2007
Hi, > I must admit that I've always thought of rev-srv as misinformation rather > than useful information. I think you've demonstrated that it's difficult > to use and doesn't reflect reality well. > > Seeing as a mechanism for auto-populating rev-srv fields with accurate > information is likely to open up a new world of pain, deprecating it > sounds like a good way of improving the accuracy of DNS data in the RIPE > database. Sounds to me like we should get rid of it as soon as possible. I certainly wouldn't miss it. And wrong / conflicting information in the RIPE db should be avoided (where posible). - Sander
- Previous message (by thread): [dns-wg] use of "rev-srv" attribute in "inetnum" (and "inet6num") objects
- Next message (by thread): [dns-wg] use of "rev-srv" attribute in "inetnum" (and "inet6num") objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]