multicast-dns | Experimental mDNS Rust wrapper around Avahi C libraries

i have a huge problem with my project in react. I'm trying to update the libraries on my project but seems something wrong happens.

This is the package.json

I have an IOT device ruining a mDNS responder, is there a way to find the device through a react-native/Expo app?

• I have found a react-native library (react-native-zeroconf). However, it requires react-native-link which expo does not support.

• I have also found a pure Java Script library (multicast-dns). However, I'm not sure whether it is possible to port that to react-native/Expo.

Should I detach and use native modules? I'm keeping that as a last resort for now.

I'm using the multicast-dns node module to attempt making this work.

Looking up custom.local in the browser gives me the console message I setup, but I'm unable to see my actual server running (which is doing so at localhost:12345, where 12345 is a dynamic number). I want to be able to see my local server when visiting custom.local. Is this possible?

Here's some code:

When I connect to the Windows IoT board normally, accessing "minwinpc.local:8080" to get to the IoT device portal works fine in the same network. However, when the same is done through the built-in SoftAP (using WiFiDirectAdvertisementPublisher), the hostname cannot be resolved. The device portal is still reachable if accessed directly through the IP (by default 192.168.137.1 on SoftAP).

This behaviour can also be observed using custom services – i.e. hostname resolution only works through external networks, but not if the IoT board itself is hosting a SoftAP.

Is there any configuration that I need to apply or any settings I need to configure using PowerShell in order to enable name resolution on the SoftAP interface?

Update

Further testing:

Initial AJ_SoftAPSsid

• Windows client: minwinpc:8080 works fine, minwinpc.local:8080 does not work
• macOS client and Windows in VMware: minwinpc:8080 does not work, minwinpc.local:8080 works fine

iPhone hotspot with DragonBoard as client

• Windows client: minwinpc:8080 works fine, minwinpc.local:8080 works fine
• macOS client and Windows in VMware: minwinpc:8080 does not work, minwinpc.local:8080 works fine

Custom SoftAP hosted by DragonBoard

• Windows client: minwinpc:8080 works fine, minwinpc.local:8080 works fine
• macOS client and Windows in VMware: minwinpc:8080 does not work, minwinpc.local:8080 does not work, only direct access through IP works (192.168.137.1:8080).

Related questions:

• MSDN forums (same question)
• https://unix.stackexchange.com/questions/385235
• https://superuser.com/questions/1239910/multicast-dns-over-softap-on-win10-iot