Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

IPv6 and RFC 2462 provide a means for hosts to configure their own IP addresses via stateless address autoconfiguration. To me this seems like the bee's knees, and it leaves me wondering why someone would want to go through the trouble of configuring a DHCPv6 server instead. I don't manage networks as a profession, so I'm guessing that there are some obvious simple reasons why one would want to support DHCPv6 that don't occur to me. Could someone please elaborate on what these reasons might be?

share|improve this question

2 Answers 2

up vote 1 down vote accepted

DHCPv6 provides more control to the administrator in assigning addresses. If you really want that sort of control over your IPv6 addresses, you don't understand IPv6 yet.

It also can be used to provide additional configuration parameters beyond the basic address/gateway supported through autoconfiguration. An example might be WINS servers, NTP servers, TFTP boot servers, and other less common options. None of which are worth the pain of deploying a DHCPv6 architecture in my opinion.

Stick with autoconfig.

share|improve this answer
Specifying TFTP isn't worth deploying a DHCP server? I'm guessing you've never deployed IP phones... –  Jason Berg Feb 28 '11 at 5:28

One thing that DHCPv6 supplies that autoconfig doesn't is DNS servers.

share|improve this answer
tools.ietf.org/html/rfc6106 For now, anyway –  DerfK Feb 28 '11 at 4:42
There's RFC 6106. If you can't use that yet your IPv4 DNS servers will probably be around until you can. Definitely not a reason by itself to use DHCPv6. –  eater Feb 28 '11 at 4:50

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.