Server addressing for renumbering ease
Brian E Carpenter
brian.e.carpenter at gmail.com
Sat Nov 6 10:45:29 CET 2010
Have people here looked at RFC5887 "Renumbering Still Needs Work"?
I'd be really interested in any comments or updates, and in ideas
how to make IPv6 renumbering systematically easier.
On 2010-11-06 18:50, Ben Jencks wrote:
> According to , they used EUI-64 addressing on their servers so that
> they could renumber easily. The common objection to that is that you
> wouldn't want to change DNS anytime you swapped a NIC (and thus a mac
> address). The obvious alternative is static addressing, but that makes
> renumbering a pain. There's also DDNS, but that seems like a bigger
> headache than either of the above . What are people here doing?
> Some other options:
> * Solaris lets you configure just the host-part, and it takes the
> network-part from RAs. This seems ideal, but it only works on solaris.
> * Use a configuration management system (puppet, chef, cfengine, etc)
> to assign addresses, so you can do find/replace in one place during
> renumbering. This would require being very careful as you risk
> breaking the connection to the config server itself.
> I know it's an old topic, but there doesn't seem to be a lot of
> guidance around. If there's a consensus I can see about making a page
> at getipv6.info.
>  http://getipv6.info/index.php/Renumbering_an_IPv6_Network
>  You can give each server only the ability to update its own name,
> but you have to give them all free reign over the reverse zone. Seems
> like a security nightmare. Alternatively you can do it through DHCP,
> but then you're back to mac-address dependence (client-identifier is
> configurable, therefore not trustworthy).
More information about the ipv6-ops