No I did not. The post was edited 2 days ago?
Oh, right, I mistakenly thought it was edited today.
When do you expect to have a solution for this problem?
Quite annoying, Iāve disabled wifi access using my omnia and activated the built in wifi in my cable modem for now.
Thanks guys for the effort!
Hello Nick. We are looking into the problem but we did not have sufficient information yet. It would really help if someone followed steps mentioned in Problem with Google and posted logs + cache files. At the moment we are preparing patched version and improved logging so we can see if it helps or not. Stay tuned.
Iād love to help but my technical knowledge of linux is a bit too limited to be comfortable to do what you describe and not mess things up :-s
What logs? Be specific.
I have these options in Omnia by default and it seems like it shouldnāt be from your post 
I will add couple more details to the information posted by miska.
Please make sure you have following options in /etc/config/resolver:
config resolver 'kresd'
option log_stderr '1'
option log_stdout '1'
option verbose '1'
I have added verbose to the list to be sure we receive extra-verbose logs.
When this is done, it is necessary to restart resolver using this command:
$ /etc/init.d/resolver restart
After restart, wait until the problem happens again. When it happens, copy logs and cache files from the router to some other place and post it. You can copy the files using e.g. scp command:
$ scp -r router:/var/log/messages /tmp
$ scp -r router:/tmp/kresd /tmp
Now post files from /tmp directory somewhere and let us know.
As I said before, we are working on making this easier. If you have time and skills for doing steps above without automation then please go ahead and post the files. It will expedite debugging process.
Thank you!
Hello,
The problem is combined with some DNS servers provider. At the moment I can only recommend changing the default DNS on the router. The solution is already on the way and maybe today or probably in a few days could be available within Relase Candidate branch. Instructions for changing is available on our website https://www.turris.cz/doc/en/howto/test_branches
Thanks for clear instructions. Iāve send private message with logs to you.
Same issue here (Western Australia) Oddly, it only affected APPLE devices. My PC could access all URLs, no problems, but two iPhone 6s and Apple Mac cannot access Google, Facebook, YouTube. But, by changing the DNS server from the Turris Router to 8.8.8.8, everything is normal again.
Thanks for that. Iāve fixed the Google/Facebook/Apple issue but now just encountered another issue ā I can no longer access the router admin page by typing the router gateway address in the browser on Chrome, but it works on Firefox. Odd.
Chrome:
This page isnāt working
192.168.15.1 didnāt send any data.
ERR_EMPTY_RESPONSE
For me every new released version have introduced new problems so Iāll avoid getting into candidate branch.
Iāll try changing DNS instead.
Hi Miska,
Just saw your post. Do you still need logs from the Turris. I fixed the problem by individually changing the DNS in each Apple device to 8.8.8.8 and that works. I saved copies of my Turris Logs and can send these to you when i get home from work tonight, if thatās useful? My config knowledge and skills are limited so might need more detailed guidance from you if you require more than what is in the log files. As I indicated in my earlier post, I only had the problem on APPLE devices (MacBook Pro, and two iPhone 6+ devices, but not on my PC Desktop running Win10)
Hello,
detailed step-by-step instructions can be found in post
Please make sure you restart the resolver or router after doing changes to configuration so it generates verbose logs.
Let me know if I can help you somehow!
1 Like
I also changed the DNS server of omnia to 8.8.8.8
All seems to work but my Android is still showing a little cross at the wifi sign but I can surf the internet (normally this means that I am connected to wifi but have no internet connection).
This means that something still isnāt 100%
Confirmed here, appeared a few days ago. It is Google, but not only (see https://gitlab.labs.nic.cz/knot/resolver/issues/179 )
Zde jsou logy: google_dns_err.tar.gz
Po nastavenĆ logovĆ”nĆ a restartu resolveru vÅ”e chvĆli fungovalo a za nedlouho pÅestal fungovat google.cz a youtube.cz, pak jsem stĆ”hl logy.
Google.com a youtube.com zdĆ” se fungujĆ, ale jsem pÅesmÄrovĆ”n na .cz.
root@turris:~# ping google.com
PING google.com (216.58.201.78): 56 data bytes
64 bytes from 216.58.201.78: seq=0 ttl=55 time=12.899 ms
64 bytes from 216.58.201.78: seq=1 ttl=55 time=13.107 ms
64 bytes from 216.58.201.78: seq=2 ttl=55 time=12.863 ms
64 bytes from 216.58.201.78: seq=3 ttl=55 time=12.881 ms
^C
ā google.com ping statistics ā
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 12.863/12.937/13.107 ms
root@turris:~# ping google.cz
ping: bad address 'google.czā
root@turris:~# ping youtube.com
PING youtube.com (216.58.201.78): 56 data bytes
64 bytes from 216.58.201.78: seq=0 ttl=55 time=11.228 ms
64 bytes from 216.58.201.78: seq=1 ttl=55 time=11.951 ms
64 bytes from 216.58.201.78: seq=2 ttl=55 time=11.728 ms
^C
ā youtube.com ping statistics ā
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 11.228/11.635/11.951 ms
root@turris:~# ping youtube.cz
ping: bad address āyoutube.czā
root@turris:~# /etc/init.d/kresd restart
root@turris:~# ping google.com
PING google.com (216.58.201.110): 56 data bytes
64 bytes from 216.58.201.110: seq=0 ttl=55 time=12.694 ms
64 bytes from 216.58.201.110: seq=1 ttl=55 time=11.909 ms
^C
ā google.com ping statistics ā
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 11.909/12.301/12.694 ms
root@turris:~# ping google.cz
PING google.cz (216.58.201.99): 56 data bytes
64 bytes from 216.58.201.99: seq=0 ttl=55 time=11.152 ms
64 bytes from 216.58.201.99: seq=1 ttl=55 time=10.359 ms
^C
ā google.cz ping statistics ā
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 10.359/10.755/11.152 ms
root@turris:~# ping youtube.com
PING youtube.com (216.58.201.78): 56 data bytes
64 bytes from 216.58.201.78: seq=0 ttl=55 time=13.269 ms
64 bytes from 216.58.201.78: seq=1 ttl=55 time=12.699 ms
^C
ā youtube.com ping statistics ā
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 12.699/12.984/13.269 ms
root@turris:~# ping youtube.cz
PING youtube.cz (216.58.201.78): 56 data bytes
64 bytes from 216.58.201.78: seq=0 ttl=55 time=11.331 ms
64 bytes from 216.58.201.78: seq=1 ttl=55 time=11.887 ms
^C
ā youtube.cz ping statistics ā
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 11.331/11.609/11.887 ms
root@turris:~#
Hello honza, Sorry to say, I have no idea regarding your problem. Too many experts here, hope someone will help you. Thanks.
I was trying to get that verbose option into kresd, but couldnāt find those extra-verbose logs anywhere. After a quick read of what /etc/init.d/kres.d I found out that the verbose option is not being read from the kresd section but the common section.
This is how my config looks like:
config resolver 'common'
list interface '0.0.0.0'
option port '53'
option keyfile '/etc/root.keys'
option verbose '0'
option msg_buffer_size '4096'
option msg_cache_size '20M'
option net_ipv6 '1'
option net_ipv4 '1'
option prefered_resolver 'kresd'
option ignore_root_key '0'
option prefetch 'yes'
option forward_upstream '0'
option verbose '1'
config resolver 'kresd'
option rundir '/tmp/kresd'
option log_stderr '1'
option log_stdout '1'
option forks '1'
That seems to do the trick.
Hello Martin,
and thank you for your work on this!
Iām really sorry to say that, here was a problem in the example I gave so the logs you uploaded are not verbose.
The corrected configuration can be found at
Please be so kind and move the verbose option to common section and do what you did again.
Thank you very much for your patience!