I'm not sure why you would have a deployed DHCPv6 server and not deploy a DNS resolver that listens to requests on an IPv6 socket. Can anybody give a rationale for this? Has anybody done this? Was it a problem?

In principle, there is nothing that would prevent you from configuring your DHCPv6 server to return an encapsulated IPv4 address, but as various people have said, this might produce a not-useful result.

I think that the idea of having a DNS resolver priority list is a reasonable answer to the problem of "what do we do if we have both IPv4 and IPv6 addresses for resolvers," but I also think that it's a complicated answer, and I do not believe that the problem it solves is a compelling one. It adds significant special-case code to the DHCP client, and I don't think it produces a useful benefit.

--------------------------------------------------------------------
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]
--------------------------------------------------------------------

Reply via email to