0(Original) Eero and mDNS
I've been having major problems with my Eero's and using mDNS (aka. .local domains). I have a couple of servers that I can reference via a .local hostname (printserver, Synology). Usually I can get to these servers just fine using their .local hostname, but randomly, and I don't know what triggers it, resolving the .local address just stops working.
Using a trace command from my MacBook Pro, which should show .local devices is blank:
~/ dns-sd -B _hap._tcp Browsing for _hap._tcp DATE: ---Wed 29 Sep 2021--- 11:55:48.917 ...STARTING... ^C ~/
The devices are on the network and I can access them via direct IP address, but that is not a solution.
The only way to get things working again is to reboot the whole Eero system. While that does get it working it's NOT A SOLUTION. I cannot just reset the whole system, kicking everyone off the wifi (people who are doing actual 9 to 5 work), just to fix an Eero problem. Until some recent Eero firmware update, .local dns resolution worked just fine (I'm not sure when it stopped).
I've emailed support several times, and their solutions consist of "... reset the Eero..."... Yeah, I know that will fix it but THAT'S NOT A FIX TO THE PROBLEM. I'm ready to consider replacing the whole system with something else (between this, and randomly the whole wifi slows down to a crawl, and I have to reboot one or more devices, I've spent too much time working around these issues...)
-
Hello johnt519 ,
I would like to assist you with this if you are willing. But I will need you to send me an email so I can locate and verify your account, review your previous tickets and start troubleshooting. I will send you a direct message with steps in how to get an email to me shortly.
-
This is required to get feature parity with mDNS when doing service discovery with the Discovery ... That is not going to happen at Linksys, Eero, Ubiquiti.
-
Well, per support's suggestion, I set a static DNS entry in the Eero, and it worked for a short time. But now .local name resolution is broken. Again. The only that changed was a firmware update in the past few days. This is getting old. I now have wait until nobody is using the wifi and reset the whole thing, so I can access my servers (Synology, Plex, etc.) Not good.
-
Just want to update this. This is STILL A PROBLEM. I was just using servers on my network, via their .local name and they just stopped working. One second it was just fine, and the next, no resolution.
Eero support hasn't been very helpful (seeing as this reply is 3 months later with little to no reply , other than "I want to help")...
-
Another month gone, and still the problem persists. After several firmware updates, mDNS keeps stopping, forcing a system reset. Confidence is low there will be a resolution to this problem... they don't seem to care.
-
Hello? @eero_support Anyone home?
This is still happening and is still a big problem.
-
Yet another month and still no answer. Just like they have no answer for my eeros that stop working and require a reset. @evan_eero_support anyone home???
-
johnt519 Thanks for posting! I have sent you a DM. Respond to me there and we can move forward.
-
-
I'm having the same issue. Works, works, works ... doesn't work. Within a matter of 10-15 minutes. Nothing in the environment changed (same device IP address, hostname, etc.) I have to either restart the device or the eero to get it working again.
-
I have the same problem, which manifests as printers (Bonjour) not working randomly.
Evan (eero support) can you take these conversations out of DMs and post a solution publicly?
-
As a footnote, I really got zero help from eero support. I have a very specific case where when the printer goes to sleep, the mDNS record drops. They told me it was a printer problem. I would normally buy that, but this problem didn’t exist with my UniFi install. It only manifested when I swapped out the UniFi equipment with eero.
-
NickTX
I would agree that support at eero seems VERY poor. Threads just sit around and turn into spam vectors (see below spam posts)
Thanks for the recommendation, I’ll look at replacing my eeros.
-
-
I received a reply from Eero support on 4/16 claiming it was going to be "submitted to the engineering team" and they will reach out when they "have further insight". And here we are, a lot of nothing.
I've got an open ticket (that's been open for MONTHS) about my Eero system (original) just dropping connection, units showing a red LED requiring a system reboot, and all I get is questions about what the layout is, what's around it. But no solutions. I'm need a system to always work, not having to reboot it almost every day, or more. And the Eero app is useless - when the system dies it would be really useful to look at the units to see what the problem is. But no, we have the "Health Check" items - that basically just start a timer and then randomly said "yup it's all good" or "Sorry we can't do a check you need to reboot". Ugh.
-
Ugh, I think I chose poorly when I replaced my Google Nest WiFi with Eero. I was tired of rebooting every few months, but I think I'm rebooting the Eeros more than once a month.
I assume no fixes for this issue? I'm about to have to reboot again because of MDNS failing.
