kirelagin:
According to [[https://datatracker.ietf.org/doc/html/rfc6762#section-6.7|Section 6.7 of the RFC]], if the query was sent not from port 5353, the responder MUST respond over unicast and, most importantly, to the same port that the query was sent from.
This is what currently prevents
dig -p 5353 @224.0.0.251
from working, since dig is expecting the response on the random port it sent its query from, but umdns, contrary to the specifiation, always sends to port 5353.
kirelagin:
According to [[https://datatracker.ietf.org/doc/html/rfc6762#section-6.7|Section 6.7 of the RFC]], if the query was sent not from port 5353, the responder MUST respond over unicast and, most importantly, to the same port that the query was sent from.
This is what currently prevents
dig -p 5353 @224.0.0.251from working, since dig is expecting the response on the random port it sent its query from, but umdns, contrary to the specifiation, always sends to port 5353.