Google Nest Wifi 2nd generation custom DNS

[pieemme]

I have unsuccessfully tried to set up my Google Nest Wifi.  Unfortunately, my auto-configuration didn't work out and I was trusting on setting up my parameters manually, as my connection has a static/public IP number.  Unfortunately I haven't been able to find how to set a custom primary DNS, which is necessary for the internet connection to work.

I googled for instructions but found that the standard instructions in Google Nest Help suggest:

How do I change my DNS server address?

1. Open the Google Home app .
2. Tap Wi-Fi   Settings   Advanced Networking.
3. Tap DNS.
4. Choose your desired public DNS server. If you choose a custom DNS server, enter a primary and secondary server address.
5. Tap Save 

Unfortunately, I couldn't find any such a thing as an Advanced Networking option in Google Home.  In Settings, there is no menu for WiFi, let alone Advanced Networking.

Kind regards

[pieemme · Accepted solution]

Thanks. I eventually managed without setting a custom DNS.  I couldn't get my Nest puck to connect with the same settings I had for my Apple AirPort Express, which had an IP number belonging to a network requiring a custom primary DNS.  I suppose this is a necessary requirement and not a redundant setting: in fact, Google Nest is not a replacement for AirPort Express.  I connected my AirPort Express, to Google Nest, after disabling wifi broadcasting from the Apple router and then created a subnet for the wifi pucks.  It's working now and there was no way to get the Google puck to work directly without setting the DNS.  It would not complete the wifi configuration.  I wonder if you can think of another fix. 

[olavrb]

Network options will appear when you have at least one Google/ Nest Wifi puck successfully added to the Google Home home in question. Then, you'll find DNS settings like so (checking my Google Home app right now):

Google Home home -> Wifi (labeled icon) -> Settings icon top right -> Advanced networking (a bit down in the list) -> DNS.

[pieemme · Accepted solution]

Thanks. I eventually managed without setting a custom DNS.  I couldn't get my Nest puck to connect with the same settings I had for my Apple AirPort Express, which had an IP number belonging to a network requiring a custom primary DNS.  I suppose this is a necessary requirement and not a redundant setting: in fact, Google Nest is not a replacement for AirPort Express.  I connected my AirPort Express, to Google Nest, after disabling wifi broadcasting from the Apple router and then created a subnet for the wifi pucks.  It's working now and there was no way to get the Google puck to work directly without setting the DNS.  It would not complete the wifi configuration.  I wonder if you can think of another fix. 

[Jeff · Accepted solution]

Hey, pieemme.

It looks like you and olavrb were able to get a fix sorted out. I just wanted to follow up real fast to see if there's anything else you needed or to see if you were all set for now. Let me know if you need any more help.

Thanks.

[Jeff]

Hi, everyone.
As we haven't had any activity here recently I'm going to go ahead and close the thread. If you have more to add, feel free to start a new discussion.
Thanks