On Jun 28, 2007, at 03:24, Jeroen Massar wrote:
If one *really* requires that there will be reverse that is
'automatically setup' (ignoring that you still have to do it for
the forward) then define in the draft the method that James
Woodyatt proposed of using synthesized reverse records for
0.0.c.f.ip6.arpa. And then simply declaring that the highest
subnet (::ffff:<64bits>)
contains at ::53 a DNS server serving reverse ip6.arpa for that zone.
I don't think I can claim full credit for this idea. I think
Christian Huitema posted first. The proposal is just for
automatically delegating the authoritative name service for reverse
DNS to ULA-C address space.
(p.s. I also like the idea of defining an anycast identifier for DNS
resolving proxy servers in the locally preferred horizon. I
understand, however, that *that* idea is more controversial-- though
I don't understand why it should be. At the risk of derailing the
topic, I'd like to mention that I know of at least one consumer
Internet gateway product that advertises its DNS proxy service with
IPv6 multicast DNS with a SRV records for _domain._udp.local and
_domain._tcp.local pointing to the AAAA records for the gateway.
This was done because there was no anycast identifier for nodes on
unmanaged networks to find their preferred DNS proxy.)
--
james woodyatt <[EMAIL PROTECTED]>
member of technical staff, communications engineering
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
