I checked the thread and would like to clarify few things. There is no such problem with updater not being able to resolve repo.turris.cz. There are people who have broken DNS configuration and should try to fix it by usual means - like disable/enable forwarding and maybe try to contact support if it doesn’t help.
I guess this all depends on the interpretation of what a problem is.
As an example. I reflash the router, make zero changes to DNS configuration and the problem exists.
Another case, I change default settings for DNS and disable forwarding, the problem exists.
So go figure what I did wrong with the DNS configuration?!?!
Another note, with these DNS problems occuring, the the 10 step wizard for initial router configuration also fails. Probably not the most optimal end user experience.
When I bought the router from the original campaign, this worked.
Something is definitely not working as expected. I’ll be happy to provide logs if required for further diagnosis.
Aren’t you connected over PPPoE (xDSL) with Turris being the PPPoE “controller”? I had this problem with the older firmwares, that setting up the connection after boot took a longer time, and the updater gave up before the connection went up.