DNS issue with punycode encoded domain names like øæå

[ACPR]

Hi,
unsure if this is in the correct forum.
I recently I noticed that any domain name with a character is unavailable via nest mesh wifi.

Have changed dns from auto to 8.8.8.8 / 8.8.4.4 without anything changing.
An example:

http://verktøy.no is handled in the background as http://xn--verkty-fya.no

Manually specifying 8.8.8.8 as dns server works:
c:\>nslookup xn--verkty-fya.no 8.8.8.8
Server: dns.google
Address: 8.8.8.8

Non-authoritative answer:
Name: xn--verkty-fya.no
Addresses: 2606:4700::6811:4478
2606:4700::6811:4778
2606:4700::6811:4378
2606:4700::6811:4678
2606:4700::6811:4578
104.17.71.120
104.17.70.120
104.17.67.120
104.17.68.120
104.17.69.120

No problems whatsoever.


But using the lan dns server adress 
ipconfig /all
...
DNS Servers . . . . . . . . . . . : 192.168.86.1 (which should pass through to 8.8.8.8)

...
- No dice

c:\>nslookup xn--verkty-fya.no
Server: UnKnown
Address: 192.168.86.1

*** UnKnown can't find xn--verkty-fya.no: Non-existent domain

[olavrb · Accepted solution]

This is a known issue that is fixed in a firmware that is currently being rolled out.

• https://www.googlenestcommunity.com/t5/Nest-Wifi/DNS-PROBE-FINISHED-NXDOMAIN/m-p/158100

[Jeff · Accepted solution]

Hi, ACPR.

If you're still seeing an issue here, go ahead and restart your system. The firmware has been fully released and it should be good to go with your system, but sometimes you need to do a restart in order for all settings to update. If you reset your system and see issues still, please let me know.

Thanks.

[olavrb · Accepted solution]

This is a known issue that is fixed in a firmware that is currently being rolled out.

• https://www.googlenestcommunity.com/t5/Nest-Wifi/DNS-PROBE-FINISHED-NXDOMAIN/m-p/158100

[ACPR]

Thanks - 
I tried to find anything about the issue, but obviously failed.

[Jeff · Accepted solution]

Hi, ACPR.

If you're still seeing an issue here, go ahead and restart your system. The firmware has been fully released and it should be good to go with your system, but sometimes you need to do a restart in order for all settings to update. If you reset your system and see issues still, please let me know.

Thanks.

[Jeff]

Hi, ACPR.
I just wanted to check in real fast to see if you saw my reply and to find out if you still needed any help on this. If you're still needing assistance, please just let me know and I'll be happy to continue helping.
Thanks.

[ACPR · Accepted solution]

Hi Jeff.

Looks like the firmware is updated and the encoded domain names work again.

Thanks for your help and for the follow-up.

[Jeff]

No problem. I'll go ahead and close up the thread, but if anything else is needed going forward, please feel free to open up a new thread.

Thanks!