I still have the problem that it comes to very many queries. My PIHole is flooded with queries.
I am on the latest version on all devices. How are the others out there? Has the situation calmed down? Am I the only one for whom nothing has changed?
I have to correct myself. It is now no longer openthread requests, but now the devices (Homepod and Homepod mini) try to find each other directly. I use the unbound service.
All requests are answered with NXDOMAIN.
So I have the following requests in this pattern, it's a few thousand per device per day.
Jun 10 00:00:25 dnsmasq[38177]: query[A] sleeping-room.local from 192.168.0.243
Jun 10 00:00:25 dnsmasq[38177]: cached sleeping-room.local is NXDOMAIN
Jun 10 00:00:25 dnsmasq[38177]: query[AAAA] sleeping-room.local from 192.168.0.243
Jun 10 00:00:25 dnsmasq[38177]: cached sleeping-room.local is NXDOMAIN
Jun 10 00:00:25 dnsmasq[38177]: query[A] sleeping-room1.local from 192.168.0.243
Jun 10 00:00:25 dnsmasq[38177]: cached sleeping-room1.local is NXDOMAIN
Jun 10 00:00:25 dnsmasq[38177]: query[AAAA] sleeping-room1.local from 192.168.0.243
Jun 10 00:00:25 dnsmasq[38177]: cached sleeping-room1.local is NXDOMAIN
Jun 10 00:00:25 dnsmasq[38177]: query[A] homepod.local from 192.168.0.243
Jun 10 00:00:25 dnsmasq[38177]: cached homepod.local is NXDOMAIN
Jun 10 00:00:25 dnsmasq[38177]: query[AAAA] homepod.local from 192.168.0.243
Jun 10 00:00:25 dnsmasq[38177]: cached homepod.local is NXDOMAIN
Jun 10 00:00:25 dnsmasq[38177]: query[A] homepod-mini.local from 192.168.0.243
Jun 10 00:00:25 dnsmasq[38177]: cached homepod-mini.local is NXDOMAIN
Jun 10 00:00:25 dnsmasq[38177]: query[AAAA] homepod-mini.local from 192.168.0.243