HomeKit DNS order bug

I think it is the case that Eero is not honoring the order of the DNS servers presented by the custom DNS feature. Perhaps it uses them in reverse order? I enter two addresses - my local PiHole DNS server and then cloudflare ( That means clients should use the first address. When HomeKit was turned it added the Eero as the first DNS server returned by DHCP. DNS clients (iPhone, Mac/PC, etc) then use the Eero for all the DNS queries. The Eero then has to forward requests somewhere after making some decisions about the DNS request (is it on the approved whitelist, for example).

What I saw was that no queries were going through my PiHole DNS server. I removed cloudflare from the custom list and then started seeing DNS requests going through my PiHole server. I didn't try reversing the order so cloud cloudflare was first to test this idea but that's my only guess without more testing. Since I disabled HomeKit (because it takes over all DNS requests for ALL devices) I can't easily test.

13replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • I've been noticing a similar issue with my HomeKit-enabled eero Pro - I have not defined ANY fallback DNS server so all DNS requests _should_ be going to the PiHole. Despite this, I can't seem to see very much. Also ensured that Local DNS Caching has been disabled (via Settings > Advabced > eero Labs)

  • I found this thread because I'm having the same issue. Also trying to have Eero configured to use my PiHole as the primary dns. 

  • Same issue here...following

  • Also having this issue and have disabled HomeKit on my eero for now. 

  • I have been having the exact same issue and, yes, disabling HomeKit fixes it but...I don't want to disable HomeKit. Is this officially a bug Eero is looking into?

  • This must be a bug, but it is has more severe issues. I lose full DNS functionality at random times, making it appear as if everything is offline. I’m concerned about disabling HomeKit if that means I have set up ~50 Homekit devices again. Will they really be removed from HomeKit? Can I remove eero via the Home app without affecting other HomeKit devices?

  • Many thanks russw , my pi-hole wasn't working at all after I set up my new Eero and I was pulling my hair out trying to figure out why. Disabling HomeKit immediately fixed it for me. 


    Eero really need to look into this as enabling HomeKit clearly breaks custom DNS.

  • I did eventually disable HomKit in eero and it resolved the headache from apparent drop-offs. It could be a combination with safety filters causing it, which also "hijacks" DNS to protect against content you want filtered out. I now see a huge speed improvement in loading content after setting up and as a custom DNS and disabling HomeKit and safety filters. I still have safety filters enabled for the kids in the house which may impact their perceived performance. is CloudFlare's new DNS which also "protects" against sites you want to avoid. (I am running pi-hole for ad filtering, with as the upstream DNS, on one laptop as an experiment--it has been working well so far.)

  • same issue here, Eero could implement a serious DNS server to solve this issue...DNS cache don't solve it! I think it's necessary activate also IGMP snooping

    Like 1
  • This is still an issue.  Running 6.3.0

  • Turned on Homekit integration as soon as I noticed that my Pro 6 got the update and BAM! Network down across the board until I stopped using my local Pi-hole server pair as the custom DNS addresses on the eero. I was running pi-hole locally passing thru DNScrypt out to NextDNS - thankfully I was able to use the NextDNS servers instead but they're only good until my external IP changes and then I gotta relink it. Or set up DDNS but man. Homekit integration broke my local pi-hole setup real bad. Not super happy about it.

  • can confirm the issue is still there. We do need a fix because since it's possible to configure the DNS I would expect requests to be forwarded, but it's not happening at all.

  • Issue still persists with the latest 6.5.0 firmware. Could anyone from the eero team please tell us if this is due to a limitation of the Homekit integration and it cannot be fixed, or if they are working on a fix? I am willing to disable the Homekit integration if this cannot be fixed.


Vote14 Follow
  • 14 Votes
  • 1 yr agoLast active
  • 13Replies
  • 512Views
  • 20 Following

Need Help? We're here for you!

We're big on support, and we want to make sure you always have the best eero experience possible. Here are several resources you can use if you ever need our help!

Quick links

Community Guidelines

Help Center

Contact eero support