As mentioned in my presentation at RIPE 54 last week we have become aware that there is an inconsistency between ipv4 and ipv6 with regard to obtaining reverse delegation. The reverse delegation procedure listed at http://www.ripe.net/rs/ reverse/reverse_howto.html has the following listed: -----snip Secondary Service by the RIPE NCC For IPv4: If your zone is a /16 reverse zone, you will need to set up ns.ripe.net as a secondary server For IPv6: If your zone is a /32 reverse zone, you may use ns.ripe.net as a secondary -----snip We think it would be a good idea to address this inconsistency, this could be done in several ways including but not limted to: Make ns.ripe.net mandatory on ipv4 and ipv6 delegations Make ns.ripe.net optional on ipv4 and ipv6 delegations Discontinue the secondary service on ns.ripe.net for new delegations. Our suggestion and preference would be to make ns.ripe.net optional on both ipv4 and ipv6 delegations. We would welcome and encourage input from the dns community on this subject. Regards Brett -- Brett Carr Manager -- DNS Services Group RIPE Network Coordination Centre Amsterdam