I'm experimenting with a Win10 IoT board that runs a web interface on minwinpc.local. This works fine in the browser, and also when I use ping.
However, when I use dig or nslookup, I cannot get resolve working.
How can ping and the browser possibly get the IP if the more basic tools fail to do the resolve?
Setup is just a DragonBoard with Win10 IoT Core, connected to an iPhone hotspot. Client that tries connecting is running macOS Sierra. No special hosts or resolve files have been adjusted.
$ping minwinpc.local PING minwinpc.local (172.20.10.3): 56 data bytes 64 bytes from 172.20.10.3: icmp_seq=0 ttl=128 time=6.539 ms
$ dig minwinpc.local any @172.20.10.1 ; <<>> DiG 9.8.3-P1 <<>> minwinpc.local any @172.20.10.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 61796 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;minwinpc.local. IN ANY ;; Query time: 51 msec ;; SERVER: 172.20.10.1#53(172.20.10.1) ;; WHEN: ... ;; MSG SIZE rcvd: 35
$ nslookup minwinpc.local Server: 172.20.10.1 Address: 172.20.10.1#53 ** server can't find minwinpc.local: NXDOMAIN