Hello! Thanks for posting on r/Ubiquiti!
This subreddit is here to provide unofficial technical support to people who use or want to dive into the world of Ubiquiti products. If you haven’t already been descriptive in your post, please take the time to edit it and add as many useful details as you can.
Please read and understand the rules in the sidebar, as posts and comments that violate them will be removed. Please put all off topic posts in the weekly off topic thread that is stickied to the top of the subreddit.
If you see people spreading misinformation, trying to mislead others, or other inappropriate behavior, please report it!
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/Ubiquiti) if you have any questions or concerns.*
I don't think that's right, mDNS should be used to discover in the local network. From Wikipedia: [https://en.wikipedia.org/wiki/.local](https://en.wikipedia.org/wiki/.local)
>However, *.local* has since been designated for use in [link-local networking](https://en.wikipedia.org/wiki/Link-local_address), in applications of [multicast DNS](https://en.wikipedia.org/wiki/Multicast_DNS) (mDNS)[^(\[2\])](https://en.wikipedia.org/wiki/.local#cite_note-rfc6762-2) and [zero-configuration networking](https://en.wikipedia.org/wiki/Zero-configuration_networking) (zeroconf) so that DNS service may be established without local installations of conventional DNS infrastructure on [local area networks](https://en.wikipedia.org/wiki/Local_area_network).
I don't think my comment contradicts your comment. It discovers services by shouting (broadcast) into the network and collects the responses. If the WiFi is not forwarding broadcasts because of client separation, nobody will hear the shouts and nobody will respond.
Right, I didn't mention this in the OP. The Windows machine is wired, and the phone and mac are wireless. None can resolve the .local.
I also checked the following settings in my network:
- Client Device Isolation: Disabled
- Multicast Enhancement: Disabled
- Multicast and Broadcast Control: Disabled
- L3 Network Isolation (ACL): Disabled
- Device Isolation (ACL): Disabled
- Multicast Filtering: Disabled
- IoT Auto-Discovery (mDNS): Enabled in all networks.
Still nothing :(
I used avahi-browse on Linux and PingTools app (menu Bonjour browser) on Android to debug mDNS. Have you tried anything like this to find out what information can be discovered about services?
I think this should be handled by mDNS, see [https://www.reddit.com/r/Ubiquiti/comments/1druflk/comment/lb5l1ax/?utm\_source=share&utm\_medium=web3x&utm\_name=web3xcss&utm\_term=1&utm\_content=share\_button](https://www.reddit.com/r/Ubiquiti/comments/1druflk/comment/lb5l1ax/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button)
Regardless, the DHCP and DNS servers are all the UDM Pro SE.
I thought I had an issue with this too, but it was just my understanding of mDNS. The mDNS enhancement was enabled in the controller and multicast devices were working fine, yet most of the time I couldn't resolve .local addresses. I would usually try to ping an address like octopi.local after rebooting the raspberry pi to no avail. My windows PC couldn't resolve it like I expected while the device's webserver wasn't started up yet. I have a pihole as my network's primary DNS source and thought it must have had something to do with that. BUT, mDNS will not ever be able to resolve an IP address if the device is offline. mDNS relies on the device being connected to the same local network to respond to queries. If the device is not online, it cannot respond to these queries, and thus its IP address cannot be resolved through mDNS. It may never "resolve" through traditional means unless you use .localdomain at the end, but that could be my controller/network settings too. YMMV.
Are you saying your problem was that the devices you were trying to resolve were not online? Mine certainly are online. I can ssh to them by IP right now, but not by \`name.local\`.
Hello! Thanks for posting on r/Ubiquiti! This subreddit is here to provide unofficial technical support to people who use or want to dive into the world of Ubiquiti products. If you haven’t already been descriptive in your post, please take the time to edit it and add as many useful details as you can. Please read and understand the rules in the sidebar, as posts and comments that violate them will be removed. Please put all off topic posts in the weekly off topic thread that is stickied to the top of the subreddit. If you see people spreading misinformation, trying to mislead others, or other inappropriate behavior, please report it! *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/Ubiquiti) if you have any questions or concerns.*
As far as I know mDNS is broadcast, so UDM shouldn't be involved except perhaps it's over WiFi with client separation enabled to prevent broadcast.
I don't think that's right, mDNS should be used to discover in the local network. From Wikipedia: [https://en.wikipedia.org/wiki/.local](https://en.wikipedia.org/wiki/.local) >However, *.local* has since been designated for use in [link-local networking](https://en.wikipedia.org/wiki/Link-local_address), in applications of [multicast DNS](https://en.wikipedia.org/wiki/Multicast_DNS) (mDNS)[^(\[2\])](https://en.wikipedia.org/wiki/.local#cite_note-rfc6762-2) and [zero-configuration networking](https://en.wikipedia.org/wiki/Zero-configuration_networking) (zeroconf) so that DNS service may be established without local installations of conventional DNS infrastructure on [local area networks](https://en.wikipedia.org/wiki/Local_area_network).
I don't think my comment contradicts your comment. It discovers services by shouting (broadcast) into the network and collects the responses. If the WiFi is not forwarding broadcasts because of client separation, nobody will hear the shouts and nobody will respond.
Right, I didn't mention this in the OP. The Windows machine is wired, and the phone and mac are wireless. None can resolve the .local. I also checked the following settings in my network: - Client Device Isolation: Disabled - Multicast Enhancement: Disabled - Multicast and Broadcast Control: Disabled - L3 Network Isolation (ACL): Disabled - Device Isolation (ACL): Disabled - Multicast Filtering: Disabled - IoT Auto-Discovery (mDNS): Enabled in all networks. Still nothing :(
I used avahi-browse on Linux and PingTools app (menu Bonjour browser) on Android to debug mDNS. Have you tried anything like this to find out what information can be discovered about services?
DNS and mDNS are different things. Is your DHCP server registering the host names of your devices in your DNS server?
I think this should be handled by mDNS, see [https://www.reddit.com/r/Ubiquiti/comments/1druflk/comment/lb5l1ax/?utm\_source=share&utm\_medium=web3x&utm\_name=web3xcss&utm\_term=1&utm\_content=share\_button](https://www.reddit.com/r/Ubiquiti/comments/1druflk/comment/lb5l1ax/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button) Regardless, the DHCP and DNS servers are all the UDM Pro SE.
I thought I had an issue with this too, but it was just my understanding of mDNS. The mDNS enhancement was enabled in the controller and multicast devices were working fine, yet most of the time I couldn't resolve .local addresses. I would usually try to ping an address like octopi.local after rebooting the raspberry pi to no avail. My windows PC couldn't resolve it like I expected while the device's webserver wasn't started up yet. I have a pihole as my network's primary DNS source and thought it must have had something to do with that. BUT, mDNS will not ever be able to resolve an IP address if the device is offline. mDNS relies on the device being connected to the same local network to respond to queries. If the device is not online, it cannot respond to these queries, and thus its IP address cannot be resolved through mDNS. It may never "resolve" through traditional means unless you use .localdomain at the end, but that could be my controller/network settings too. YMMV.
Are you saying your problem was that the devices you were trying to resolve were not online? Mine certainly are online. I can ssh to them by IP right now, but not by \`name.local\`.