<div>
<div class="content wysiwyg-content">
We are looking to deploy Microsoft DirectAccess and as part of that we are planning to Dual Stack IPv6 on various server subnets to enable end-to-end communication between the remote users and the servers (instead of it being NAT64/DNS64)<br />
<br />
We do not however have an IPv6 internet connection. &nbsp;<br />
<br />
Whilst I’m confident this will work well for the server/client communication, Will this not cause any issues with the DA clients trying to access the internet through the direct access tunnel? (as the DNS server will likely return a 'true' IPv6 address in the DNS response to the client). <br />
<br />
Also, for all the servers configured with IPv6 (including the AD/DNS servers), will they have any sort of performance impact when attempting to reach public internet dual-stacked websites? i.e. as it has a global unicast address will it prefer IPv6 and try to reach it with IPv6 first?
</div>
</div>


We are looking to deploy Microsoft DirectAccess and as part of that we are planning to Dual Stack IPv6 on various server subnets to enable end-to-end communication between the remote users and the servers (instead of it being NAT64/DNS64)

We do not however have an IPv6 internet connection.  

Whilst I’m confident this will work well for the server/client communication, Will this not cause any issues with the DA clients trying to access the internet through the direct access tunnel? (as the DNS server will likely return a 'true' IPv6 address in the DNS response to the client). 

Also, for all the servers configured with IPv6 (including the AD/DNS servers), will they have any sort of performance impact when attempting to reach public internet dual-stacked websites? i.e. as it has a global unicast address will it prefer IPv6 and try to reach it with IPv6 first?

Windows Server and IPv6

The Windows operating systems have distinct methodologies for designing and implementing networks, and have specific systems to accomplish various networking processes, such as Exchange for email, Sharepoint for shared files and programs, and IIS for delivery of web pages. Microsoft also produces server technologies for networked database use, security and virtualization.

Windows Networking

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

Networking software modules are interfaced with a framework implemented on the machine's operating system that implements the networking functionality of the operating system. The best known frameworks are the TCP/IP model and the OSI model. Systems typically do not use a single protocol to handle a transmission. Instead they use a set of cooperating protocols, sometimes called a protocol family or protocol suite.[9] Some of the best known protocol suites include: IPX/SPX, X.25, AX.25, AppleTalk and TCP/IP. Other protocols indirectly related to networking include the hypertext transfer protocol (HTTP) and its related technologies, Dynamic Host Configuration Protocol (DHCP), Domain Name Server (DNS) and other Internet protocols.