We have a collection of Windows Server 2012 R2 virtual machines running our organization (DC, Fileserver, Exchange Server, Remote Access server, and an LOB server). They all have static IPv4 addresses which is the way I've always done things.
But I'm being forced to start to learn how IPV6 works because of some issues I've been having.
The servers have IPV6 enabled and set to just obtain the address automatically. I try not to touch it and most of the time it's been working. But I've been experiencing some very slow performance on my Remote Access Server's reverse proxy (IIS Application Request Routing) and it turns out the problem is because the IPV6 address of my Application Server is wrong, or not responding.
The server has the regular ethernet adapter, which has an IPV4 and an IPV6 address. Both of those addresses appear to work fine. But it also has this "Microsoft 6TO4 Adapter" which also has an IPV6 address. The Microsoft 6TO4 Adapter address is what appears to be registered in my DNS, and it does not respond to any pings or requests.
I've never really dealt with IPV6 before and I'm not sure why the 6TO4 adapter even exists, or how it is supposed to be set up. Should I be assigning static IPV6 addresses, and if so how do I determine what addresses to use? Should the 6TO4 adapter not be used? Or is there something wrong with it?
What's the right way to set this up?