Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, February 15, 2018 1:05 PM
Dear all,
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 DHCPv6.
While the A record for the DHCPv4 assigned IPv4 address gets successfully registered on the DNS server after startup of Windows 10, the IPv6 address gets not registered after startup.
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. Leaving the computers on for several hours leads to successful registration of both IP addresses as well.
We have tested and can observe this behaviour with Windows 10 Professional 1607, 1703 and 1709 with the latest cumulative updates installed. It is reproducible in physical environments where clients are connected to Cisco 2960X switches and in a test lab where Windows 10 clients are connected to VMware vSphere Standard switches.
Windows 7 clients are not affected and successfully register both their IPv4 and IPv6 address right after startup on the DNS server.
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.
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.
The DNS server is based on Windows Server 2008 R2 SP1. The zone of the clients is directory integrated and set to allow both secure and unsecure dynamic updates.
DNS 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.
Windows 10 clients with statically configured IPv6 address are updated successfully in DNS during startup of Windows 10.
Output of ipconfig /all on Windows 10 client:
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:
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:
As written above, in Windows 7 both the IPv4 and IPv6 address are registered both after startup. Theoretically this could be caused by a timing issue - i.e. if the IPv6 address is not yet present when the dynamic update request is sent to the DNS server. 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. And in addition to that - Windows 7 is not affected.
Also, the operating system should take care of such issues. Once a new IP address is available, it must start the process to register it in DNS. Currently, clients configured with both IPv4 and IPv6 are only reachable over their IPv4 address when accessing their DNS names.
I actually think this is a bug in Windows 10. Has anybody observed similar behaviour and can confirm my findings?
Thanks
Michael
All replies (10)
Friday, February 16, 2018 8:29 AM
Hi Michael,
Thank you for your very detailed description.
As the we need some time to analyse the symptom deeply, please create a startup script with command line ipconfig /registerdns as a workaround.
As soon as we get any information, I will reply to you.
At last, please feedback the issue to Microsoft through Feedback Hub application.
Bests,
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Friday, February 16, 2018 1:38 PM
Hi Joy-Qiao,
thank you very much for your reply, I'm happy to hear that someone is hearing me and going to look into it. In the meantime I followed your suggestion and also submitted the issue through the Feedback Hub application:
feedback-hub:?contextid=862&feedbackid=980b32b7-857c-4f56-b755-6388bd0a4edd&form=1&src=1
Please get back to me in case you need more information. I'm happy with contributing to analyze and solve this problem. I also consider this as quite important since more and more enterprises are moving dual stack now
Thanks,
Michael
Monday, February 19, 2018 3:42 AM
Hi Michael,
Thanks for your feedback, I have seen this:
When you are using IPv4 and IPv6 dual stack on the same DHCP interface, you must configure one dynamic profile for both the IPv4 and IPv6 subscribers. You cannot run IPv4 and IPv6 subscriber sessions over the same interface if you configure separate dynamic profiles for IPv4 and IPv6.
For more information, click IPv4 and IPv6 Dual Stack in a DHCP Access Network
Also this guide from Cisco, you can refer to:
http://docwiki.cisco.com/wiki/IPv6_and_IPv4_Dual_Stack_on_a_Branch_Router_Configuration_Example
Please Note: Since the websites are not hosted by Microsoft, the links may change without notice. Microsoft does not guarantee the accuracy of this information.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Monday, February 19, 2018 7:59 AM
Hi Kate,
thank you. However, this is not related to my problem and a little bit out of context as it is about the proper setup of Juniper and Cisco solutions for Dual Stack.
As I have written above, the registration of both addresses is working fine in Windows 7 with DHCPv6. Also, it does work in Windows 10 when registering the addresses manually using ipconfig /renew.
My problem is that when using IPv6 with DHCPv6, the IPv6 address does not get registered in DNS after startup of Windows.
Thanks
Michael
Monday, February 19, 2018 11:13 AM | 1 vote
Hi Joy-Qiao,
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.
Scenario 1 - IPv6 address gets registered in DNS
In case the client either has no IPv6 address obtained via DHCPv6 yet or an existing DHCP lease has expired, Windows 10 goes through the following DHCPv6 process:
1. Clients sends DHCPv6 Solicit
2. Server sends DHCPv6 Advertise
3. Clients sends DHCPv6 request
4. Server sends DHCPv6 reply
Wireshark Capture of this process:
In this case, the Windows 10 client updates both the IPv6 and IPv4 address in DNS. The DNS Dynamic Update packet contains both the IPv6 and the IPv4 address.
Scenario 2 - IPv6 gets not registered in DNS
In case the client already has obtained an IPv6 address from the DHCPv6 server and the lease is still valid, Windows 10 performs the following DHCPv6 activities on startup:
1. Clients sends DHCPv6 Confirm
2. Server sends DHCPv6 Reply
Wireshark Capture of this process:
In this case, the Windows 10 client only updates its IPv4 address in DNS. The DNS Dynamic Update packet contains only the IPv4 address.
In addition to that, IPv6 DNS server information is not refreshed on the client in scenario 2. That is, if a DNS server gets added or removed to the corresponding DHCPv6 scope, the client does not update its DNS server settings. This is despite the fact that the DHCPv6 reply (in return to the DHCPv6 confirm packet) actually includes the new DNS server settings:
I actually think this is a bug in the Windows 10 DHCPv6 client, as even Scenario 2 is working fine in Windows 7 and the DNS update contains both the IPv6 and IPv4 address.
Tuesday, February 27, 2018 7:59 AM
Hi Michael,
I would apology for my late reply.
Considering the complexity and the difficulty of the issue, we would suggest to create a ticket with the link below. You could discuss with IT professional engineer directly and they should have more resources to research the issue.
Thank you for your understanding.
Bests,
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, February 27, 2018 11:46 AM
Hi Joy-Qiao,
thanks, I will create a ticket with Microsoft in this case. In the meantime (for all others who might be interested) I performed some additional testing and found out that there are some circumstances where the dynamic update of the IPv6 AAAA record does not work in Windows 7 either and does work in Windows 10 even in case the lease is still valid and only renewed by the DHCPv6 confirm/reply messages.
In case it does work in Windows 10, the DHCPv6 confirm/reply messages are sent two times each:
In this case, the dynamic DNS update also contains the IPv6 address. If the DHCPv6 confirm/reply messages are only sent once, only the IPv4 address is included and updated in DNS.
The main problem is: If there was no DHCPv6 lease existing or an exiting one has expired and the client has to go through the whole DHCPv6 solicit/advertise/request/reply process, the IPv6 address is always included in the dynamic DNS update. In case the lease is renewed with confirm/reply messages, it sometimes works and sometimes not - this seems to be true for both Windows 7 and Windows 10 according to my current testings.
Thanks
Michael
Thursday, June 7, 2018 9:12 AM
Hi Michael,
We are seeing similar problems on Windows Server. Seems that the problems have started within the last few months, so we expect a Windows update to be the cause of the problem. When the client gets a new IPv6 address via SLAAC it does not register the new address in DNS (most of the times). If running ipconfig /registerdns the address is correclty registered.
Did you start an official case with MS Support - and have you received any fix from them?
Kind regards,
Anders
Anders Heick | Conscia A/S
Monday, June 11, 2018 9:24 AM
Hi Anders,
we created a support incident with Microsoft (ticket IT 118022717715752). Unfortunately, the ticket was open for two month and then closed without offering any solution. I don't think they even looked into this in more detail.
At the moment the issue is not critical for us so we're just going to wait until it is solved by any upcoming update in the future (hopefully).
It would be nice if you could get back to this thread in case you find a solution.
Thanks
Michael
Monday, June 11, 2018 9:43 AM
Michael, thank you for the update. I will keep you posted in case we find a solution.
/Anders
Anders Heick | Conscia A/S