#Ipv6 not connected windows 10 update#
#Ipv6 not connected windows 10 manual#
#Ipv6 not connected windows 10 registration#

I have performed some additional testing today and found out that the DNS registration of the IPv6 address after startup of Windows 10 works if the DHCPv6 lease of the IPv6 address has expired. Has anybody observed similar behaviour and can confirm my findings? I actually think this is a bug in Windows 10. Currently, clients configured with both IPv4 and IPv6 are only reachable over their IPv4 address whenВ accessing Once a new IP address is available, it must startВ the process to register it in DNS. And in addition to that - Windows 7ДЄlso, the operating system should take care of such issues. However, I have also tested this with having both the client and the DHCP server in the same network segment (so there is no relay or router between them that might cause delays) and this also doesn't make a difference.

#Ipv6 not connected windows 10 update#

if the IPv6 address is not yet present when the dynamic update request is sent to the DNS server. Theoretically this could be caused by a timing issue - i.e. Wirshark trace of client's DNS update on DNS serverВ after manually forcing ipconfig /registerdns on the clientВ - you can see that the DNS update includes both the IPv4 and IPv6 address:ДЄs written above, in Windows 7 both the IPv4 and IPv6 address are registered both after startup. Wirshark trace of client's DNS update on DNS server right after startup - you can see that the DNS update only includes the IPv4 address but not the IPv6 address: Output of ipconfig /all on Windows 10 client:

Windows 10 clients with statically configured IPv6 address are updated successfully in DNS during startup of Windows 10. The zone of the clients is directory integrated and set to allow both secure and unsecure dynamic updates.ДNS server and clients are in-time-sync and there are no DNS client event errors (8012) on the Windows 10 client that indicate problems with registering the IPv6 AAAA record during startup. The DNS server is based on Windows Server 2008 R2 SP1. The DHCP server is based on Windows Server 2016 and set up with the standard configuration, that is it only registers PTR records on behalf of the clients and not A or AAAA records.

#Ipv6 not connected windows 10 manual#

Since manual registration works fine and Windows 7 is not affected at all I don't think the problem is related to an inproper configuration of the network or DHCP/DNS server.

Windows 7 clients are not affected and successfullyВ register both their IPv4 and IPv6 address right after startup on the DNS server. Where Windows 10 clientsВ are connected to VMware vSphere Standard switches. It is reproducible in physical environments where clients are connected to Cisco 2960X switches and in a test lab We have tested and can observe this behaviour with Windows 10 Professional 1607, 17 with the latest cumulative updates installed. Leaving the computers on for several hours leads to successful registrationВ of both IP However, forcing a manual registration by using ipconfig /registerdns is working as expected and both the IPv6 and IPv6 are successfully registered on the DNS server. IPv6 address gets not registered after startup. On the DNS server after startup of Windows 10, the While the A record for the DHCPv4 assigned IPv4 address gets successfully registered We are currently implementing Dual Stack (IPv4/IPv6) for our networks and have found that the dynamic registration of DNS IPv6 AAAA records does not work correctly on computersВ running Windows 10В that obtain their IPv6 address viaВ stateful