Windows 10: Windows 10 does not receive mDNS response

Hi,I have windows 10 enterprise OS version 22H2 OS build 19045.4291I am currently testing the mDNS Multicast DNS feature on my device Nucleao_STM32U575ZI_Q development board, which is connected to my Windows 10 Enterprise laptop via WiFi. Device act as a Access point and Laptop as a station.The issue I am encountering is that when I send a request from my laptop to the device, the device send a response but the laptop does not capture it, it captures the response when I toggle IPv6 setting in WiFi properties. Interestingly, when I tested the same scenario using windows 11. it worked as e

:)

 

Windows 10 spams network with invalid mDNS response packets

Windows 10, in its default configuration, will spam its local networks by responding to all mDNS requests with null response packets.

This appears to be in violation of RFC 6762 Section 6, which states:

"A Multicast DNS responder MUST only respond when it has a positive, non-null response to send, or it authoritatively knows that a particular record does not exist."

It is becoming an increasing problem on our networks, where compliant non-Microsoft equipment will often respond to an invalid mDNS packet by generating an error message, cluttering system logs and wasting resources. Additionally it is creating absurd levels
of multicast traffic on or network wherever there are several windows 10 hosts.

As Windows 10 adoption rises, so does the need to filter out these error-generating packets. Just a handful of Windows 10 PCs on a subnet may broadcast hundreds of invalid packets per minute, causing an equal number of error messages to be generated on some
devices, particularly those running an Avahi-based zeroconf implementation.

I have not been able to find a way to report this bug directly to Microsoft, but if it isn't going to be fixed anytime soon, corporations might be forced to start filtering these
erroneous mDNS packets from Windows 10.

The key issue is that this issue has been reported all over the place but it appears we are unable to report this bug directly to microsoft. How do we do this?

Windows 10 spams network with invalid mDNS response packets

Debian #751288: Avahi-daemon is noisy · Issue #10 · avahi/avahi

Bug #1342400 “avahi-daemon constantly reporting “Invalid respons...” : Bugs : avahi package : Ubuntu

 

mDNS support in Windows 10

It is my understanding that mDNS and DNS-SD support has been added to Windows 10 out of the box (per Windows 10 spams network with invalid mDNS response packets
), 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

 

Ported number doesn't show up as SIM's MDN

Thanks for your suggestion JG2yang1, but since I posted this question back in February my network provider firstly suggested they try a network refresh (which didn't change anything) and then a replacement SIM. With that new SIM, the MDN setting simply
disappeared. The phone no longer indicates any such setting as Settings>About>More Info>MDN: or
(phone)>Settings>My Number Is... I also learned that I am not the only Lumia owner on that network (EE in UK) who has experienced this issue.

Do you know the anwer to my original question: Is it the case that Windows Phone owners have no way to edit the displayed MDN?