I have 3 hubs that I have pointed to an internal pi-hole dns server. I’m seeing a ton of DNS queries from these hubs for reverse lookups of 0.0.0.0. Any idea how to get these things to stop?
I’m getting about 1 million of these a day on in DNS server log. It does several per second.
Mar 4 16:15:40 dnsmasq[1441]: query[PTR] 0.0.0.0.in-addr.arpa from 10.0.0.72
Mar 4 16:15:40 dnsmasq[1441]: cached 0.0.0.0.in-addr.arpa is (null)
Mar 4 16:15:40 dnsmasq[1441]: config error is REFUSED
Which hub do you have? Perhaps try restarting the hub?
I have a v2 hub and do not see any of these records in my pihole.
Also here I have 2 connect home pro and 1 connect home, in bridge mode. All do the same thing.
dropped from about a million per 24h to 30.000 something pointing the 0.0.0.0 address (IPv4 and IPv6) to openwrt.lan (the smartthing hub itself). You can query the hub directly at port 53 to see if it resolve the domain openwrt.lan to 127.0.0.1
I am having the very same issue. How do you point the 0.0.0.0 address to openwrt.lan?
-Chris
Anyone find out what is causing this?
Mine are beating my DNS server so much they keep crashing it, tens of thousands of requests mainly PTR to 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa and 0.0.0.0.in-addr.arpa. I am about to pull them out and use them as hockey pucks for all the good they do.
Same problem here. Seeing around 10,000 DNS requests per second from my single Smartthings hub to api.smartthings.com. It’s blowing through my paid resolver quota in a day.