-
Notifications
You must be signed in to change notification settings - Fork 13.3k
No way to resolve mDNS hostnames #4706
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
From #4591 (comment)
I am looking forward to this, but until then I make do with what we have. |
note: after a while it stops working, only use it a few times between restarts |
I'm also interested in this feature. |
@palmerabollo It stops working after about 20 resolutions, and it also blocks all other connections. Probably some kind of resource leak. |
Glad to find this thread. I found myself wondering why there was no ESP8266 equivalent to the ESP32 Going to try mDNSResolver for now. |
I assume that someone made their own library and it had some basic functionality. And because it had useful features it was included in this framework. I don't believe it was ever claimed to be a full implementation. |
Closing in view of #5442 with a full rewrite of mdns. |
The ESP8266 can do everything else with mDNS (advertise services, query services, set it's hostname), apart from the very important thing of querying hostnames.
ESP32 can do it with the MDNS.queryHost function, but it only wraps the one from the sdk, which lives inside a compiled binary. So it's no use for backporting it to the ESP8266.
This is all more unfortunate because the netBIOS library also cannot resolve hostnames
edit: madpilots mDNSResolver did the job, but the functinality should be part of the built in library
The text was updated successfully, but these errors were encountered: