Deploying IPv6 in Server 2008 and Server 2008 R2
Microsoft has made changes to common features of obtaining and using IP addresses. With the end of IPv4 coming, DNS support and DHCP are the two biggest changes.
One change known as Intra-Site Automatic Tunnel Addressing Protocol or ISATAP. Server 2008 will not generate ISATAP if no ISATAP router is in your network. This prevents computers and nodes from connecting to your server using IPv6 packets that are encapsulated in IPv4 packets. ISATAP can be enabled manually to support any IPv6 apps that you have.
This can be done by going to a command prompt and typing: netsh interface ipv6 istap set state enabled
FYI – Windows Server 2003, Windows 7, Windows Vista and Windows XP (with service packs) will allocate an address to the ISATAP interface even when the hostname (ISATAP) cannot be resolved.
Planning on configuring an ISATAP server? You can enable a Server 2008 DNS to serve responses to any queries for an A record fo the hostname ISATAP.
Open the registry. Navigate to the entry -
Remove the ISATAP entry and restart your DNS Server. If you have multiple DNS Servers, you will need to make this change if ISATAP is defined in the DNS.
When you plan for IPv6, you’ll need to decide to use public (globally aggregatable) or private ip addressing. So here you go – if you decide on public, you have to get an IPv6 address prefix from your ISP. Note: If they don’t provide support of IPv6 at this time, you can get one from a tunnel provider.
Many administrators are deciding to use private IPv6 addresses (known as locally unique address). This allows them to become familiar with IPv6. They can then get global addresses later. During this transition, examine all of the devices in your network and look for devices that will need to be upgraded. IPv6 and IPv4 are designed to work together for now. The primary infrastructure (during your IPv6 examination) of your network that takes computers out to the internet are the computer’s operating system, switches (managed), DHCP Servers, DNS Servers, firewalls, load balancers (gateways/load balancers) and your router. Managing and migrating to Server 2008 and utilizing private IPv6 gets you to a point where all you have to do is wait on your ISP. Once you have your infrastructure in place, this will give you time to ‘play’ with your network and IPv6.
Most networks today (medium to large) use private IPv4 addresses. These networks usually rely on a NAT device such as a firewall or router that allows a transition from private (10.x.x.x, 172.16.x.x or 192.168.x.x) to a public number.
So what happens once your devices are in place? Routers will begin to support router solicitation. In other words, your router will advertise a unique IPv6 address prefix on each interface that attaches to it. So if you use global (public) aggregatable IPv6 addresses, you will probably get an IP address that begins with 2001::/16. If you get locally IPv6 address, they will begin with fd00::/8.
And just for the record, Dawn, Mike and I will pull our hair out before it is over.
Look for our future article on configuring the server.