>>>>> On Mon, 10 Jun 2002 14:43:08 -0700,
>>>>> Alain Durand <[EMAIL PROTECTED]> said:
> An issue that is overlooked in this discussion is reverse path
> DNS lookup for site local addresses.
> Today, with IPv4+NAT on my home network, I simply point my
> stub-resolvers to my ISP DNS resolver. It's simple, and works
> fine, at least until I try to do reverse DNS lookup for my internal
> addresses. Then it just fails. Some applications that I run on
> my local LAN don't work well or wait forever for timeouts,
> because they can not resolve 1.1.168 .192.in-addr.arpa.
> If I had enough IPv4 address space, I could get my ISP
> to populate the DNS reverse maps, and my problem would
> be solved.
> I would expect that IPv6 will help me here by giving me a
> global prefix (although I agree that getting my ISP to populate
> a v6 reverse map is somehow more complex than in IPv4),
> but if, according to the address selection rules, my system will prefer
> site local addresses for internal communication, amd I'll back to square
> 1.
(this is not directly related to the site-local address issue any
more)
Aside from whether site-local addresses are good, acceptable, or bad,
I believe the described problem means we'll have to try to not rely on
the reverse lookup in IPv6 much more than in IPv4.
draft-ietf-dnsop-inaddr-required-03.txt should be taken seriously in
IPv6.
JINMEI, Tatuya
Communication Platform Lab.
Corporate R&D Center, Toshiba Corp.
[EMAIL PROTECTED]
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
