the DNS resolving on my Turris Omnia is unstable, and has been for months. Is that a known issue? Is there a fix?
The Turris Omnia often (several times a week) stops resolving some (seemingly random) domain names, both for websites and mailservers. At the same time, many other domain names resolve fine.
Less often, DNS resolving completely stops working.
I can always fix these issues with a reboot.
I can sometimes fix these issues by going to http://192.168.0.1/config/dns/ and clicking on âTest connectionâ. After that, all domain names are resolved correctly.
Background: I have no IPv6 connectivity, all other tests result in âOKâ.
Device Turris Omnia - RTROM01
Turris OS version 3.6.3
Kernel version 4.4.59-627f0117679bc72ef5e58881035f567a-4
OK. I suspect it might be about NS reputation tracking, related to recent serious problems that affected some people.
If you want to work around it, Iâd suggest to use forwarding (which has other disadvantages). I would ask you to confirm my suspicions by generating logs, but the support UI for that is being reworked ATM and probably doesnât work.
I gave up already. Omnia had constant issues with accessing webpages and mailboxes. Itâs been like that since the very beginning. All magically went away when I enabled DNS forwarding. This however rendered DNSSEC not working. So, all the gems like âhave your own dns resolverâ and âenjoy safer surfing with DNSSECâ are unfortunately no-go for me. Quite a shame.
I agree the DNS resolver issues are unfortunate. Iâve been using knot-resolver for months without encountering problems in resolvability, but there have been many people with issues.
So apparently we are still waiting for a fix? My ability to resolve addresses is terrible. I am getting ready to buy a new router. Like others have said we are being asked to edit config files via putty⌠I donât even know how to enable SSH on the router.
Edit: SSH works now. I guess maybe an update resolved that, so at least I can SSH if need be.
That linked problem was fixed long time ago, and I havenât noticed anyone confirming such problems since then. I assume you have Turris Omnia in recent version.
What is your DNS settings in Foris? (forwarding, DNSSEC, connection test results)
These are the symptoms I experienced, which I now can fix (thanks to your explanation) by manually correcting the /var/run/resolver.pid file.
For a little while every 10 minutes, no DNS resolution occurs while - due to a bug - kresd restarts. While kresd is restarting, DNS requests appear very slow; sometimes they time out and the browser thinks the domain name does not exist. A few seconds later, kresd is back up and it works nicely for the next 10 minutes.
My symptoms were similar to jfrodshamâs short description, âbrowser hangs on âResolving Hostâ for long periods and sometimes times out.â