Requests to support only DHCPv6 identity
G.Eustace at massey.ac.nz
Thu Mar 29 00:38:13 UTC 2012
The DUID is global to the computer and as such does serve as a unique identifier.
When equipment has multiple NICs, this would only cause an issue, as I see it, if both NICs are in the same network. If, as would I believe be the more normal case, they are indifferent networks, then I believe this is fine as an address out of the appropriate scope would be allocated for each.
What happens with the DDNS is something I haven't tested. I believe the reverse lookup, the PTR would be added correctly but I suspect that any existing AAAA would probably be deleted and replaced with the 2nd one.
In theory one can have multiple AAAA for the same host.
As already stated in an earlier email, I am not sure that DHCPv6 has been particularly well thought through. I would still *REALLY* like to hear from anyone who has what they consider a good working deployment.
From: dhcp-users-bounces+g.eustace=massey.ac.nz at lists.isc.org [mailto:dhcp-users-bounces+g.eustace=massey.ac.nz at lists.isc.org] On Behalf Of ???
Sent: Thursday, March 29, 2012 11:55 AM
Subject: Requests to support only DHCPv6 identity
Because DUID Conflict in window2008 system installed two NIC.
So We should choose an Only and not repeat the identity identifier. For a variety of applications client.
Identity should not be repeated, whether in any environment.
Detailed questions from:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dhcp-users