Configuring a DHCPv6 server
The DHCP Server service in the following versions of Windows
Server supports both stateful and stateless address
autoconfiguration via DHCPv6:
-
Windows Server 2012
-
Windows Server 2008 R2
-
Windows Server 2008
You can configure a computer running Windows Server 2012 as
either a DHCPv6 stateless server or a DHCPv6 stateful server by
performing the following steps:
-
Begin by installing the DHCP server role on your
server.
-
Assign static IPv6 addresses to the DHCPv6 server
interfaces that will be listening for incoming DHCPv6 request
messages.
-
Open the DHCP snap-in, and expand the IPv6 node beneath
the server node.
-
To configure DHCPv6 options for stateless address
autoconfiguration, right-click on the Server Options node
beneath the IPv6 node and select Configure Options as shown
here:
Then configure the DHCPv6 server options as desired. For
example, you could configure option 23 DNS Recursive Name Server
IPv6 Address List as shown here:
-
To configure DHCPv6 options for stateful address
autoconfiguration, right-click on the IPv6 node and select New
Scope as shown here:
Then use the New Scope Wizard to specify a name and
description for the scope, an IPv6 subnet prefix, and other
information required.
6. IPv6 transition technologies
The ultimate goal of IPv6 is for IPv4 to eventually be retired
and all nodes on all TCP/IP networks to use only IPv6. However, such a
goal might take years, or even decades, to achieve. In the meantime,
IPv4 and IPv6 nodes must be able to interoperate on the same network
so that communications will not be disrupted, and IPv6 transition
technologies make this possible. Windows platforms can be used to
implement the following IPv6 transition technologies:
-
ISATAP This transition
technology allows IPv6/IPv4 nodes on an IPv4-only intranet to use
IPv6 to communicate with each other and across the IPv6
Internet.
-
6to4 This transition
technology provides automatic tunneling that allows IPv6/IPv4
hosts to establish IPv6 connectivity with each other across the
IPv4 Internet. However, implementing 6to4 requires that the edge
device (router) use a public IPv4 address.
-
Teredo This transition
technology provides automatic tunneling that allows IPv6/IPv4
hosts to establish IPv6 connectivity with each other across the
IPv4 Internet even when IPv4 network address translation (NAT)
devices need to be traversed. Because of this capability, Teredo
is more suitable than 6to4 for small office/home office (SOHO)
environments that use NATs to hide their private IPv4 addresses
from the Internet.
In addition, Windows platforms support the following
IPv6-to-IPv4 traffic translation technologies:
-
NAT64 This technology is used
to allow IPv6-only nodes to access IPv4-only hosts. The
DirectAccess feature of Windows Server 2012 uses NAT64 to enable
DirectAccess clients (which act as IPv6-only nodes) to access
hosts on an IPv4 corporate network.
-
DNS64 This technology is used
to map IPv6-only address record (AAAA) name queries to IPv4
address record (A) name queries. Using DNS64 together with NAT64
enables IPv6 nodes to initiate communication with IPv4-only nodes
with no changes to either node.
-
PortProxy This technology
allows IPv4/IPv6 TCP traffic to be proxied to IPv4/IPv6 TCP
traffic at a different address. The technology is useful when
nodes cannot communicate using either IPv4 or IPv6.
The following section describes one of these transition
technologies (ISATAP) in more detail.
