You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hello, maybe someone can help me to deal with this issue...
i want to discover a amazon fire device. the dns search on the shell (on mac) works very well with this command
dns-sd -B _amzn-wplay._tcp local
This comand response with an instance name like this "amzn.dmgr:649079E36FF650C95604A3397843E704:QZT4YaSve2:325301"
the next call receive the device info dns-sd -L "amzn.dmgr:649079E36FF650C95604A3397843E704:QZT4YaSve2:325301" _amzn-wplay
and response with
... can be reached at 192-168-5-103.local.:53725 ...
so how can i archive the same result with multicast dns ?
currently i just use the basic sample script with my custom name mdns.query({ questions:[{ name: '_amzn-wplay._tcp.local', type: 'A' }] })
he will find the device but no addition information are given
hello, maybe someone can help me to deal with this issue...
i want to discover a amazon fire device. the dns search on the shell (on mac) works very well with this command
dns-sd -B _amzn-wplay._tcp local
This comand response with an instance name like this "amzn.dmgr:649079E36FF650C95604A3397843E704:QZT4YaSve2:325301"
the next call receive the device info
dns-sd -L "amzn.dmgr:649079E36FF650C95604A3397843E704:QZT4YaSve2:325301" _amzn-wplay
and response with
... can be reached at 192-168-5-103.local.:53725 ...
so how can i archive the same result with multicast dns ?
currently i just use the basic sample script with my custom name
mdns.query({ questions:[{ name: '_amzn-wplay._tcp.local', type: 'A' }] })
he will find the device but no addition information are given
got a response packet: { id: 0, type: 'response', flags: 1024, questions: [], answers: [ { name: '192-168-5-103.local', type: 'A', class: 1, ttl: 3600, flush: true, data: '192.168.5.103' } ], authorities: [], additionals: [] }
any ideas ? thanks a lot
The text was updated successfully, but these errors were encountered: