We are currently preparing for IPv6 only network deployment and struggle to find a unique server identification.
In our previous setup, we used mac address as servers primary identification. We were then able to assign the server always the same address.
E.g. we needed to perform upgrade from wheezy to jessie and rather then apt-get dist-upgrade, we reinstalled the server. As we use puppet for configuration, it all took 15 minutes and server was up, fresh and perfectly running again with the same IP and DNS name.
Unfortunately, we are currently not able to achieve this with IPv6 as the server with every OS (Linux, PXEBoot kernel, ...) has different DUID, which means for every OS different IPv6 address.
In our setup, we use mikrotik as DHCP server.
How would you manage situation like this?
Update #1: It seems it is currently not possible:
- https://www.insinuator.net/2015/02/is-rfc-6939-support-finally-here-checking-the-implementation-of-the-client-link-layer-address-option-in-dhcpv6/
- http://blog.bronislavrobenek.com/post/64383333742/ipv6-security-in-enterprise-network
I was able to find a patch (http://alter.org.ua/soft/fbsd/isc_dhcpd/) for isc-dhcp-server that fixes this, but it is not global solution and I can't apply that on cisco or mikrotik devices.
Update #2: We have decided to leave mikrotik platform as we outgrown the capabilities of this platform. We are currently preparing new "infrastructure" server based on linux, that will run https://dhcpy6d.ifw-dresden.de/ (besides other services such as openvpn for ipmi, ...).
