google hub won't connect after setting up sleep sensing when using custom DNS

[hayzeus]

On my network, I do not allow any port 53 tcp/udp out my internal network for privacy reasons.  I have 2 internal dns servers that run dns-over-https.  All my internal devices are set to use the two internal DNS servers for name resolution.  

My daughter recently started setting up sleep sense on her google hub but stopped.  Ever since then, the google hub will no longer connect to the internet unless I allow the google hub to initiate dns queries to whatever DNS servers it wants to query, it refuses to query the DNS servers that are given to it via my dhcp settings and I see no queries from the IP address of the google hub to my internal dns servers.

Please fix this problem so that the device will respect the dhcp dns settings and query the dns server that it is supposed to.  It seems like DNS might be hard coded for some reason with sleep sense.

[Muddi · Accepted solution]

Hey folks,

I have some great news to share! This issue on Nest Hub (2nd gen) should now be resolved and you can get back using your devices with a custom DNS network. If for some reason you’re still experiencing problems, please update this thread and let us know.

Cheers,

Muddi

[lucidelirium]

My Nest Hub is unable to connect to Wi-Fi during setup (or function aftwards) without access to Google's DNS 8.8.8.8/8.8.4.4. Is this stated in any terms of service? 

[hayzeus]

Hello, I am having the same issue and it seems recent.  Here is my post on it along with a reply from princess who may or may not be associated with google.  This is atrocious that an internet device doesn't respect DHCP settings nor allow for custom DNS settings.  I really can't think of any legitimate reason for this change.

https://www.googlenestcommunity.com/t5/Speakers-and-Displays/google-hub-won-t-connect-after-setting-...

[lucidelirium]

Concur that this is a recent change. Will try the feedback options available but would love to hear from a dev...

[hayzeus]

If you have a device capable of doing so, nat internal traffic destined to 8.8.8.8 and 8.8.4.4 back to your pihole servers.  Not the best workaround for the time being, but at least it works.

[Princesss]

Hey everyone, 

Thanks for posting.

Since this is the same discussion with the other thread, I'll go ahead and move it to the main thread so we can share some tips there.

Best,

Princess

[lucidelirium]

Good call! I added a loopback for 8.8.8.8 on pihole, static route,  and it works. May try NAT in the future. Thank you!

*added startup script to persist

[antistes]

I recently bought a nest hub and run into the same problem. There are actually two... I needed to block the google DNS in my private network in order to cast to the nest devises (front door camera if it rings). I can't do that using an IP. The google displays only accept HTTPS. So no problem... just configure a local DNS server to handle that. Exactly that is impossible if those devices hardcode the DNS IP addresses into their firmware. The other ones at least use my  private DNS if I block the Google ones and it still works. Not so with this device which ONLY uses Googles DNS servers...

Please fix it. I also filled out the feedback.

[Links2004]

has there been any change on the nest hub side?
my nest mini is working fin, but my nest hub does not use the DNS server of my network 😞

[durotan]

Hi, I'm having the same problem.  The workaround  mentioned above was to NAT internal traffic destined for 8.8.8.8 & 8.8.4.4 to pihole servers.  I have a  UDM PRO, can anyone help in how to do this?

Will google/alphabet/nest be fixing this?

[lucidelirium]

Below is basically what I did on pihole. My router has a static route for both 8.8.8.8 and 8.8.4.4 to my pihole. You can run the script or reboot.

nano dns.sh
#!/bin/sh
sudo ifconfig lo:0 8.8.8.8 netmask 255.0.0.0 up
sudo ifconfig lo:1 8.8.4.4 netmask 255.0.0.0 up
ctrl+x; y (save it)
chmod +x dns.sh

crontab -e (open with nano)
@reboot sh /home/pi/Documents/dns.sh
ctrl+x; y (save it)

[brkaminski]

I'm still experiencing this issue with a brand new out the box 2nd gen hub.

[Dabijja]

Same here 🤕

[Dabijja]

May not be the right solution for everybody here but I have just managed to connect my new NestHub gen2 by .... disableing Parental Control (both from ISP and router). Strange?

[Muddi]

Hey everyone,

@Dabijja: Thanks for sharing the steps.

Please try joining the Preview Program. Follow the steps below to know-how:

1. Open the Google Home app.
2. Touch and hold your device's tile.
3. At the top right, tap Settings > Device information > Preview Program.
4. If you can't find the "Preview Program," we're unable to accept new members at this time. Please continue to check back as opportunities become available.
5. Choose whether to receive email notifications by moving the slider to the right or left. Note: It is recommended to allow email notifications so you’ll know when new updates are pushed to your device.
6. If you opt-in to email notifications, you'll be asked to sign into your Google Account if you haven’t already.
7. Review the contents of that page, and tap the Join Program.
8. Review the contents of the page, then tap Ok, get it.

Let me know if that fix the issue.

Cheers,

Muddi

[rheinen]

I still have the same problem. It is still not possible to use a custom DNS server. Even when I'm subscribed to het Preview Program.

[rheinen]

My hubs have been updated to version 47.9.4.447810048 and for now it is possible to use other DNS.

[antistes]

I can confirm that. It finally seems to work. Thank you.

[riccume]

Agree, it is working now with version 47.9.4.447810048. Thank you.

[jlaham]

Apparently this is not confined to just the Nest Hub 2nd Gen. Pretty much all Nest devices in my home continuously attempt to reach 8.8.8.8 and 8.8.4.4, my firewall logs are pretty much a laundry list of dropped DNS packets from Nest devices on my network. I’ve even been able to pinpoint this as the reason one of my Nest Cams continuously attempts to renew its DHCP lease every 50 seconds, it tries to reach Google’s DNS, fails and then tries to reconnect, renews the lease, and repeat.

Recommendation to the product team(s), if you’re going to force the use of Google DNS servers (which is already very suspicious), then at least be good house guests and connect to Google DNS servers over HTTPS for our privacy.