North American Network Operators Group|
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical
RE: IPv6 reverse lookup - lame delegation?
-----BEGIN PGP SIGNED MESSAGE----- Mark Andrews wrote: > The correct fix to this will be to just stop making IP6.INT > queries. > > The best think that could be done is for the PTB to install > "IP6.INT. DNAME IP6.ARPA." *now*. This will allow the legacy > resolvers to get a answer and allow vendors to stop shipping > legacy aware resolver in the vague hope that they will get > a answer from IP6.INT that they didn't get from IP6.ARPA. >From RFC3363: 8<---- 4. DNAME in IPv6 Reverse Tree The issues for DNAME in the reverse mapping tree appears to be closely tied to the need to use fragmented A6 in the main tree: if one is necessary, so is the other, and if one isn't necessary, the other isn't either. Therefore, in moving RFC 2874 to experimental, the intent of this document is that use of DNAME RRs in the reverse tree be deprecated. - ---->8 It will indeed work, but not work everywhere. Redhat boxes for instance apparently croak on it. Legacy resolvers might quite possibly include support for it though so one might be on the safe side there. I guess DNAME is getting used more for a purpose for which it wasn't intended at first ;) Greets, Jeroen -----BEGIN PGP SIGNATURE----- Version: Unfix PGP for Outlook Alpha 13 Int. Comment: Jeroen Massar / http://unfix.org/~jeroen iQA/AwUBQClxTCmqKFIzPnwjEQLsEACfTWllm2ul5Eb8Umo1wFOca+KHuC8An3yh Vaz4pe0/rWXv6km0/7/nNzu4 =cGP8 -----END PGP SIGNATURE-----