* Tony Finch:
On Thu, 2 Dec 2010, Florian Weimer wrote:
* Tony Finch:
On Wed, 1 Dec 2010, Niall O'Reilly wrote:
Me too. I think that the approach which Chris is suggesting sits more in LIR territory than with the RIRs.
What about legacy allocations where the DNAME needs to be placed in a reverse zone maintained by RIPE?
I don't think such a case actually exists. Could you be more specific?
Ah, now I look they seem to be ARIN's zones. (Our allocations include 128.232, 129.169, and 131.111.)
It should still work. In the parent, you'd have: 169.129.in-addr.arpa. IN NS ns1.example.net. 169.129.in-addr.arpa. IN NS ns2.example.net. And ns*.example.net. would serve 169.129.in-addr.arpa. IN DNAME reverse.example.com. This scheme breaks down when you delegate individual /32s because DNAME does not apply to the name itself, only its children. -- Florian Weimer <fweimer@bfk.de> BFK edv-consulting GmbH http://www.bfk.de/ Kriegsstraße 100 tel: +49-721-96201-1 D-76133 Karlsruhe fax: +49-721-96201-99