Latest firmware release seems to have broken support for Danish æ, ø and å in URLs

[drklug]

Hi,

After 14150.43.80 firmware updates it is no longer possible to access URLs using Danish characthers like æ, ø and å.

This used to work, and as soon as I switch off wifi to 3/4/5g it works again.

Following URLs are examples of sites that no longer works and returns "DNS_PROBE_FINISHED_NXDOMAIN";

 - https://www.svømmetider.dk

 - https://jordbærbonden.dk

- https://århus.dk 

The URLS maps to these using punycode;

https://xn--jordbrbonden-bdb.dk/

https://xn--rhus-poa.dk/

The problem is reproducible on PC and iphones - and it used to work until 2-3 weeks ago.

As a workaround I can add a local rule in the host file specifying the IP address for the domain, but that is cumbersome and doesn't work on phones etc.

/Martin

[MichaelP]

Yep – another user reported this here: https://www.googlenestcommunity.com/t5/Nest-Wifi/DNS-PROBE-FINISHED-NXDOMAIN/m-p/145177 

It's been escalated, but no word on a fix as yet.

[Jeff]

Hey, drklug.

Thanks for the report on this. Obviously this is an issue we'll push to the forefront. Thanks also to MichaelP for helping raise awareness on this. I'll get this passed on to our internal teams ASAP.

[Jeff]

Hi again, drklug.

Just as an update this has been brought to our internal teams and they're actively working on the fix for this right now. Thanks again for bringing it to our attenion. If you have any questions, just let me know.

Thanks.

[drklug]

Thanks - any Update on a date for a fix?

Alternativet, is it possible to downgrade to previous firmware?

[Jeff]

Hi, drklug.

I'm don't have a timeline on the fix quite yet, but I have seen a lot of back and forth communication among the internal teams on this. They're definitely working fast to tackle the issue. As far as firmware downgrades go, there's no way to roll back firmware updates. I'm sorry for the issues you're seeing with the current release, but a fix will be coming soon. Let me know if you have any other questions.

Thanks.

[Jeff]

Hey, all.

The fix for the issue has been found and it will be rolling out real soon to your devices. I don't have the timeline for the fix delivery, but we do know it's inbound. If you see the fix arrive for you, feel free to report here so others can see it's starting to arrive.

Thanks!

[Jeff · Accepted solution]

Hi, again.

I got word that the fix is being pushed out right now and by the end of the week most everyone should have it. If you aren't seeing the update in place by Monday, give your network a restart and see if that applies the settings for you. If by that point you're still seeing issues, please let me know right away.

Thanks.

[StianVolstad]

Fixed for me as well now.. thanks

[t0wer001]

Just set up a domain alias with "æ", and thought I messed up the 301 redirect, but I'm happy I found this thread.

I'm experiencing the exact same as reported by the OP.

[StianVolstad]

+1 for this issue

[StianVolstad]

My workaround which is very simple and straightforward is to connect my in-browser VPN ... 

[drklug]

I have version 14150.43.81 and can confirm it fixes the issues.

[Jeff]

It's good to see this is clearing up now that the update is out. Again, if you are still seeing any problems and haven't restarted your network, give that a try and you should see the update applied.

Thanks!

[Jeff]

Hey, everyone.
I wanted to check in and see if there was anybody still seeing this issue. By now the fix should be on everyone's devices and this should no longer be a problem for anyone. If you are having troubles, just let me know.

Thanks.

[Jeff]

Hi, everyone.
Just one quick final check in here since activity has slowed down. We'll be locking the thread in the next 24 hours, but if you still need help, I would be happy to keep it open. If there's more we can do, just let me know.
Thanks.

[Jeff]

Hi, all.
As we got our resolution here, I'm going to mark this one as resolved. Thanks to all who helped and contributed. If anyone has any other needs, please feel free to open up a new thread.
Thanks!