You first need to check the settings of your network interface to see if IPv6 is enabled via Start -> Control Panel -> Network and Sharing Center -> Change adapter settings -> Right click on your network card and choose Properties. In Windows 2008 this should be enabled by default, but check it nonetheless:
While you're there, open the IPv6 Properties by selecting the Internet Protocol Version 6 (TCP/IPv6) row and clicking on Properties. Enter your IPv6 settings achieved from your internet service provider there:
Since publically routable IPv6 addresses are no longer a scarse thing to have like with IPv4 addresses, it's actually possible and advisable to assign a dedicated IPv6 address to each WebApplication hosted within your SharePoint farm.
However, currently SharePoint 2010 does not support a direct IPv6 assignment in IIS to a WebApplication yet. You need to leave them all unassigned in the IIS bindings, so a direct benefit of assigning multiple IPv6 addresses is not yet there unfortunately.
You can add additional IPv6 addresses by clicking on Advanced and clicking Add within the IP addresses section:
Verify that you're having IPv6 connectivity to the outside world by pinging ipv6.google.com:
Now click OK on all the open network dialog boxes to save the changes and close them.
Open up Internet Information Services Manager (IIS) via Start -> Administrative Tools -> Inernet Information Services (IIS) Manager and browse using the tree at the left to your server name -> Sites -> SharePoint WebApplication. Right click on the WebApplication and click on Edit Bindings:
Click on Add to add a new binding to the IPv6 address. Select the IPv6 address you wish to bind to this webapplication from the IP address list. There is no need anymore to enter a host name since you will not be sharing this IP address with other webapplications anymore.
After clicking OK to add the new binding, it will be added to the bindings list:
You're all set. Your SharePoint 2010 WebApplication is now ready to accept IPv6 traffic!
Added comment 11 January 2012:
Once you have bound a specific IPv6 address to ANY of your IIS webapplications as instructed above, you will no longer be able to create a new SharePoint WebApplication using either PowerShell or via the Central Admin UI. A message will be displayed that "System.FormatException: Input string was not in a correct format". See
this MSDN topic.
The only way to avoid this bug is to leave all WebApplications bindings in IIS unassigned state. This elminates the benefit of allowing an IPv6 to be dedicated to a WebApplication without requiring a AAAA DNS record. Unfortunately there is no other way. Unless you find it acceptable to unassign all of your webapps in IIS temporarily whenever you want to create a new WebApplication in SharePoint 2010 and bind them back after doing so, this is the only option.
You can verify if your host can receive IPv6 traffic over port 80 by using the following online tool. Be sure to enter the IPv6 address in the host to scan field:
For more information, check out the
MSDN article on using SharePoint 2010 in an IPv6 environment.