Not turning queries from MDNS (5353) to DNS (53)

[montehansen]

I have a domain of .local. As a result, certain devices will force the use of mdns instead of dns. A WireShark capture on the proxy device evidences the traffic for mdns, but not the resulting dns traffic which is what I thought this proxy would do. Am I missing something?

Thanks in advance.

[montehansen]

Any thoughts would be appreciated.

[miselin]

Sorry for the delay.

I'd like to clarify a a few things to try and understand why this is not working correctly for you:

• that there is visible multicast traffic seen on the proxy host on port 5353, for destination address 224.0.0.251,
• and, if this traffic is seen in the traffic capture, no outbound traffic on port 53 is seen,
• and there's nothing seen aside from "Now listening for mDNS queries..." on the terminal in which you ran proxy.py?

For example, I'd expect to see something like this:

$ ./proxy.py
Now listening for mDNS queries...
mDNS query from 192.168.0.13:5353
    for _raop._tcp.local. [12]
    No result for a lookup of type 12 for _raop._tcp.local. CLASS32769 PTR
    for _airplay._tcp.local. [12]
    No result for a lookup of type 12 for _airplay._tcp.local. CLASS32769 PTR

... for the following traffic capture ...

09:08:39.684843 IP 192.168.0.13.5353 > 224.0.0.251.5353: 0 [2q] [1au] PTR (QU)? _raop._tcp.local. PTR (QU)? _airplay._tcp.local. (78)

I recommend using the mdns-lookup.py tool on another system (not the same as the proxy) to create queries as well, as you have more control over when queries are created that way.