Reverse lookups and PTR packages

Lets say I know the ip of brunhilde.local and want to know its host name (i.e. brunhilde.local!). So I build up my query like this:

mdns.query({questions:[{name:'26.178.168.192.in-addr.arpa.',type:'PTR'}]});

What I can see when I monitor the network using Wireshark is that the mDNS query is malformed and type and class are missing:

26.178.168.192.in-addr.arpa: type Unused, class Unknown (3072), "QM" question

A valid query (e.g. generated using dig -p 5353 @224.0.0.251 -x 192.168.178.26) would be as the following:

26.178.168.192.in-addr.arpa: type PTR, class IN, "QM" question

unfortunately I didn’t have enough time to get deep into the code to see if I’m doing something wrong (or undesired) or is it a valid bug. Any help is appreciated.

[thenewwazoo]

Progress! If I specify rinfo in my query, I see a response back on the network. The code now looks like

        let resolver = mdns({
            multicast: true,
            ttl: 1,
            port: 0,
        });

        resolver.query({
            flags: 1 << 8 | 1 << 5,
            id: getRandomInt(1, 65534),
            questions: [
                {
                    name: reversed,
                    type: 'PTR',
                    class: 'IN'
                },
            ],
            additionals: [
                {
                    name: '.',
                    type: 'OPT',
                    udpPayloadSize: 0x1000,
                },
            ],
        }, {
                      port: 5353,
                      address: "224.0.0.251",
        });

~The problem I’m having now is that nodejs never seems to receive the response datagram that I can see in packet capture.~ Looks like I had a bug in my response handler code, and I am now successfully doing reverse lookups.

[yan-foto]

@thenewwazoo it seems that @mafintosh is most probably like the rest of use have limited time for maintenance 😃