Windows Server 2016 IPv6 Hell

Our network has a Sonicwall, Windows Server 2016 DC, Exchange Server 2016, and Windows 10 clients.

We need to enable IPv6 on our network for an application.

The problem is if the servers have IPv6 enabled, Windows clients prefer IPv6 for communication including authenticating on the domain. Authentication and Exchange stop working if DNS records are not setup properly.

1. The DC must have a static IPv6, because it is the DHCP server.

2. Setting a static IP through the GUI does not disable DHCP client, so it must be disabled using the powershell command: Set-NetIPInterface Ethernet -AddressFamily IPv6 -DHCP Disabled

3. The DC does not register the static IPv6 address in DNS.

4. AAAA record for the DC registered manually in DNS is removed on the next refresh.

5. If DHCP is enabled, the DC adds the correct records to DNS, however an additional AAAA record for the DHCP assigned IP is also added which breaks the system.

6. If I create a DHCP reservation for the DC that is the same as the static IP, everything works until the DC is restarted.

After the reboot, the GUI displays "Obtain an IPv6 address automatically" again which does not work, as that IS the DHCP server and it cannot reach itself without an address.

I am unable to find documentation on properly configuring IPv6 for static IPs in Windows Server 2016. If anyone can help I would greatly appreciate it.

Depending on the size of the Enterprise, kill DNS scavenging, if it is a smaller environment.

If it is larger, than that solution could be a bit messy and you may want to run a script occasionally that will scavenge with exceptions. I wrote something in PS sometime ago, if this is something you may need, lemme know.