Due to a corrupt database today, I had to restore the hub and sadly I got confirmation that it used internally stored DNS servers.
I had a complex network outage and the hub joined the network on a diferent IP than what I usually had it on.
The originally “assigned” IP had a hole in the firewall for the DNS requests as I suspected that in some cases, it ignores the DHCP assigned DNS.
Is that a desired behavior for the hub since it comes packaged with a master DNS server in the platform?
You can manually override DNS, but not via DHCP.
DNS servers assigned by the DHCP server were not used to “dial out”.
The hub negates these and issues a request on port 53 outside of these IPs. I have a crude firewall that blocks everything 53 except a handful of IPs.
I can replicate this at any time. I set the hub on an ip in the blocked 53 range, it will not use the LAN DNS.
Can you PM me your hub's id? I can check the engineering logs for clues.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
Download the Hubitat app
