It is my understanding that mDNS and DNS-SD support has been added to Windows 10 out of the box (per https://social.technet.microsoft.com/Forums/en-US/b334e797-ef80-4525-b74a-b4830420a14e/windows-10-spams-network-with-invalid-mdns-response-packets?forum=win10itpronetworking
), but when attempting to ping a node that advertises via mDNS using the standard .local TLD, Windows 10 cannot resolve it.
From a command prompt of a clean install of Windows 10:
C:\>ping far-80770005.local
Ping request could not find host far-80770005.local. Please check the name and try again.
C:\>
However, I can ping it directly using the IPv6 address:
C:\>ping fe80::230:64ff:fe2b:9123
Pinging fe80::230:64ff:fe2b:9123 with 32 bytes of data:
Reply from fe80::230:64ff:fe2b:9123: time=1ms
Reply from fe80::230:64ff:fe2b:9123: time<1ms
Reply from fe80::230:64ff:fe2b:9123: time<1ms
Reply from fe80::230:64ff:fe2b:9123: time<1ms
Ping statistics for fe80::230:64ff:fe2b:9123:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
C:\>
From another Windows PC with Bonjour installed:
C:\>ping far-80770005.local
Pinging far-80770005.local [fe80::230:64ff:fe2b:9123%11] with 32 bytes of data:
Reply from fe80::230:64ff:fe2b:9123%11: time<1ms
Reply from fe80::230:64ff:fe2b:9123%11: time<1ms
Reply from fe80::230:64ff:fe2b:9123%11: time=1ms
Reply from fe80::230:64ff:fe2b:9123%11: time<1ms
Ping statistics for fe80::230:64ff:fe2b:9123%11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
C:\>
Further, from the same machine using the node name (without the .local) it appears that Windows 10 will implicitly try mDNS as I can see the query in wireshark, but prefers the IPv4 address over the IPv6 address.
Note that from Windows machines with Apple's "Bonjour Print Services for Windows" or "iTunes for Windows" installed or Linux and OS-X based machines the mDNS ping to .local nodes works as expected.
When will this functionality be corrected by Microsoft such that name resolution will attempt mDNS for nodes with .local domains explicitly used by the user, and to use the IPv6 ahead of IPv4?
-Jim
