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.

4replies 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. 

Vote3 Follow
  • 3 Votes
  • 14 hrs agoLast active
  • 4Replies
  • 35Views
  • 5 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