# Wifi versus mDNS **URL:** \ **Category:** Installation and Getting Started\ **Created:** [December 27, 2021, 4:29pm UTC](https://amplipi.discourse.group/t/wifi-versus-mdns/68 "2021-12-27T16:29:14Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![rick](https://yyz2.discourse-cdn.com/free1/user_avatar/amplipi.discourse.group/rick/32/36_2.png) [@rick](https://amplipi.discourse.group/u/rick)\ **Post date:** [December 27, 2021, 4:29pm UTC](https://amplipi.discourse.group/t/wifi-versus-mdns/68/1 "2021-12-27T16:29:14Z")
Still having trouble seeing the AmpliPi from my WiFi-connected mobile phone apps. I am not connecting via a guest-SSID, and I have tried turning off the 5GHz band for a while. I see the AmpliPi using an android network analysis app, but only if I ping its IP-address. Pinging amplipi.local does not work from the phone (via-WiFi). I assume the AmpliPi mobile app (from the Google Play Store), uses mDNS lookup to find the AmpliPi. I have an Eero Pro mesh wifi network, which provides IP addresses that end in 192.168.7.xxx – so, maybe this creates an atypical wifi subnet? I am told that mDNS does not broadcast properly through some vendors’ WiFi-routers, (because the broadcast creates too much overhead). Some folks recommend a third-party “bypass server”, or disabling a “filter”, or using a “sniffer”, but I have yet to figure out how to implement any of these techniques on the proprietary Eero app, (Eero-owners do not get normal web-app browser-access to their router-settings). Will update if I, or someone smarter than me, discovers a solution. ---
**Author:** ![linknum23](https://yyz2.discourse-cdn.com/free1/user_avatar/amplipi.discourse.group/linknum23/32/6_2.png) [@linknum23](https://amplipi.discourse.group/u/linknum23)\ **Post date:** [December 28, 2021, 5:33pm UTC](https://amplipi.discourse.group/t/wifi-versus-mdns/68/2 "2021-12-28T17:33:47Z")
I am sorry you are still having trouble with this. One thing that I would like to correct here is that AmpliPi does **not** host its own WiFi network, the hardware only has an Ethernet connection (note the CM3+ module we use does not have built in WiFi like many pis). Also `.local` resolution does not work on android. More details [here](https://android.stackexchange.com/questions/49188/how-to-get-mdns-working-for-chrome-on-android). As for troubleshooting mDNS on the eero, I found the following thread, where an eero engineer responded, may be helpful: [https://www.reddit.com/r/eero/comments/azyvf2/cannot\_reliably\_get\_local\_resolution\_working/](https://www.reddit.com/r/eero/comments/azyvf2/cannot_reliably_get_local_resolution_working/) We are working on being able to specify a IP-address/URL in the app and trying other automatic search methods to make this as painless as possible. See [here](https://github.com/micro-nova/Amplipi-Mobile-App/issues/7) for details. ---
**Author:** ![rick](https://yyz2.discourse-cdn.com/free1/user_avatar/amplipi.discourse.group/rick/32/36_2.png) [@rick](https://amplipi.discourse.group/u/rick)\ **Post date:** [December 28, 2021, 8:01pm UTC](https://amplipi.discourse.group/t/wifi-versus-mdns/68/3 "2021-12-28T20:01:16Z")
SOLVED: AmplPi required a power cycle, which likely updated the mDNS records to make mDNS broadcast properly over the mesh-Wifi. I had also changed the DNS server to Cloudflare, from the default being my ISP, but I doubt that made any difference. I was all about the reboot. My AmpliPi mobile app (on Wifi) can now find the AmpliPi and it now works perfectly. Is this a bug, or can you just add a power cycle button to the PC web-app? Walking into a server closet, to unplug a rack-mounted AmpliPi, is not an intuitive solution to mNDS updates. ---
**Author:** ![linknum23](https://yyz2.discourse-cdn.com/free1/user_avatar/amplipi.discourse.group/linknum23/32/6_2.png) [@linknum23](https://amplipi.discourse.group/u/linknum23)\ **Post date:** [December 28, 2021, 8:30pm UTC](https://amplipi.discourse.group/t/wifi-versus-mdns/68/4 "2021-12-28T20:30:36Z")
Awesome. We have been meaning to add a restart button! We’ll see if we can add that soon.