-
Notifications
You must be signed in to change notification settings - Fork 13.3k
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
Search mDNS when resolving DNS names #2373
Comments
This would be great. I'm trying to get mdns to work right now just for this purpose but not having any luck. @madpilot -- do you have a functioning |
@n8henrie Not right now - I finally have master running in my IDE, so I'm hoping to have a poke around this week. |
Interesting lwip info here: http://savannah.nongnu.org/task/?10238 |
should be possible to pull latest stable lwip (2_0_2) and add to options #define LWIP_DNS_SUPPORT_MDNS_QUERIES 1 |
we should actually port the mdns from ESP32. It has host and service queries and all. I need to add a couple of features before merging though. |
well, the root cause for not being able to resolve .local addresses lies in lwip, but certainly parity between ESP32 and ESP8266 would be nice. |
I ended up writing a small library that does this: https://github.com/madpilot/mDNSResolver |
@me-no-dev will you be porting the esp32 mdns? no hurry. Also, it may make more sense after migrating to lwip2. |
@madpilot I assume from your last comment that your mDNSResolver addresses this issue? |
i hope some not so full version of it can be ported. 3 interfaces and IPv6 on ESP32 make things a bit intensive and i do not know how 8266 will coop even with v4 on 2 interfaces. But there is a way I imagine to port most of it (once done) |
Automatic switchover to MDNS lookup in HostByName() for .local hostnames would forcibly pull in the MDNS code for all users, which is undesirable. I suggest a simple app function along the lines of:
Closing. |
Feature request: When automatically resolving domain names, would it be possible to search using the mDNS broadcast address if the domain name ends with .local?
If the domain name ends with .local, using a DNS server ip of 224.0.0.251 and a port of 5353 is all that needs to happen, so there is minimal code change.
If someone wants to point the right file, I'm happy to change it and put it in a PR.
The text was updated successfully, but these errors were encountered: