> > Hello Scott , A little more definition to the picture would be > nice . Tia , JImL > The potential mismatch between IPv6 and classic DNS is that an IPv6 unicast address is structured in two parts: the network identifier (the high 64 bits) and an Interface ID (the low 64 bits). Half of the Interface IDs are globally unique, the other half are assigned locally within the network. For the half that are globally unique, a query system could be defined to look up that address and return the network(s) where it was found. Even if it is a local identifier, if the host network is known by multiple network identifiers the interface id would still be the same across all of the possible identities. (There may be a loophole there, but that is clearly the intent of the spec.) Again, a directory service could optimize its representation of the data to take advantage of these correlations. If such optimizations are done, the question remains of whether they should be part of the DNS service. The "non-optimizing" solution minimizes the code impact and encourages early support for IPv6 on networks that remain primarily IPv4. In my opinion, any optimizations are best left until after a measurable problem is starting to develop and mobile IP solutions are fully deployed, as that the solution is likely to overlap with mobile support.