Why is Tempest using Google DNS over my local DNS

I just ran some reports on my firewall and noticed that my Weatherflow hub it using names services from 8.8.8.8 (Google) vs. what my router hands out. Is there a reason your device doesn’t configure DNS based on what is sent out though DHCP? It looks like it was resolving mqtt.weatherflow.com

From my router:

image

From the DNS query:

image

1 Like

Since FW 171 the Google DNS exists as a backup since we had many cases where dhcp didn’t give a DNS, a DNS not working as expected to resolve the servers from Weatherflow or way to late.
I just checked my network and the hubs do use the DNS from my pfsense (non Google ones)

That’s about what I know of the story. Since that time we didn’t see many cases like we did before where the hub couldn’t ‘find’ the Weatherflow servers.

and mqqt is one of the links used.

1 Like

OK thanks…strange that it chose to go to Google on mine. I did a manual DNS query to both local and Google and they both resolved the same address for mqtt.weatherflow.com.