2.3.9.176 - DNS still a mess

[ramset]

@dennypage

FWIW, my firewall blocks direct access to external DNS

+1 to this.

I do get the occasional hiccup, where it says no cloud connection available, however, running the network tests (including trace or ping on hostname where DNS request IS resolved using the defined DNS server) works.

I’ve been “barking” about the hard coded DNS for quite some time:

C5/C7 update 2.2.5.119 - DNS issues - cloud connection unavailable

Updated to the latest version 2.2.5.119 The update was successful however a DNS relate problem surfaced after the reboot. While my C5 took the update and worked flawlessly after the reboot, the C7 apparently was stuck on a ?hard coded? DNS (blocked at router level - i only allow a specific DNS). I tried setting the DNS manually in the new feature available for that, it saved my DNS but no queries went through that. The hub still used the other one. I restored to 2.2.4.158 and the issue persi…

Platform Hard-coded DNS ignores DHCP/Manual assigned DNS

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?