goont

> I vastly prefer it to having to ship mdnsresponder alongside my application though.

That's what I'm seeking to avoid too. I'll have to take a closer look at the device enumeration API next time I circle around to the Windows port. Thanks for sharing your experience with it.

Have you shipped anything using that API? I'm just a bit weary of wasting time on another half-baked solution.

And are you sure the Windns.h API is deprecated? I could have sworn it only showed up last year.

Notably Android doesn't support mDNS as part of general hostname resolution. (There is the NSD API available but you have to explicitly use it, and the browsers do not.)

There is an API exposed in Windns.h but it doesn't work very well. It's awkward to use and doesn't pick up on services being added and removed. See `DnsService*`, etc in https://docs.microsoft.com/en-us/windows/win32/api/windns/.