Nest Thermostats and custom DNS

[Lostenka]

I found an interesting issue:
I have a lot of IoT devices connected to my router, have a Synology NAS and use the Synology DNS server set on this NAS. My router is set to send the internal IP of Synology to all connected devices as a primary DNS (using this to access local devices by names and not by IPs). However, everything (all switches, computers, laptops, tablets) works fine except Nest Thermostats and Nest Protects (not smart thermostats - only cheap ones, learning thermostats work well). When the above-mentioned devices get Synology DNS IP as a primary DNS, they fail to connect to the internet and thus unavailable to monitor/control.

Any ideas why this could happen?

[RenzJ]

Hi Lostenka,

Thanks for posting here in the Google Nest Community forum. For the Nest Learning Thermostat and Nest Protect, we suggest using a 2.4 GHz band connection. Nest Protect and the 1st and 2nd generation Nest Thermostats only support 2.4 GHz communications. If your access point is dual-band (broadcasts both 2.4 and 5 GHz signals), make sure that it is broadcasting a 2.4 GHz signal.

You can check Update Wi-Fi network and router settings for more information.

Feel free to let us know if you have more questions in mind. 

Cheers,

Renz

[Lostenka]

Thank you! I appreciate your desire to help, but unfortunately, your answer is unrelated. Never in my question I mention that I switched to a 5Ghz network. The network itself didn't change - neither the frequency nor the security settings. The only thing that was changed is the default primary DNS server. 

[RenzJ]

Hello Lostenka, 

I apologize for the confusion. We're not recommending using a different DNS server due to restrictions. You might want to use the Google settings, where the primary DNS server is 8.8.8.8 and 8.8.4.4 on the secondary.

Let me know if it works.

Best,

Renz