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]/
[db-wg] RFC 2317-style Reverse DNS Delegation in the RIPE Database
- Previous message (by thread): [db-wg] RESTful API for create, delete and update
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Anand Buddhdev
anandb at ripe.net
Wed Sep 21 17:09:13 CEST 2011
[Apologies for duplicates] Dear colleagues, In April 2011, Denis Walker sent a proposal to the DNS and Database Working Groups outlining some reverse DNS-related changes to the RIPE Database. You can see the full proposal here: http://www.ripe.net/ripe/maillists/archives/db-wg/2011/msg00080.html I'm happy to report that this proposal has been fully implemented. This means that: - Dashes in the third octet of a DOMAIN object are no longer allowed - Dashes in the fourth octet are now allowed A dash in the fourth octet allows for RFC 2317-style reverse DNS delegation for Provider Independent (PI) address allocations which don't fall on octet boundaries. For this second change, we converted all existing delegations into appropriate DOMAIN objects in the RIPE Database. We will update the reverse DNS "how-to" on the RIPE NCC website over the next few days. If you have any questions, please send an email to <dns at ripe.net>. Regards, Anand Buddhdev DNS Services, RIPE NCC
- Previous message (by thread): [db-wg] RESTful API for create, delete and update
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]