
NextDNS not working anymore with the windows client or YogaDNS
Starting today, the windows client is not working anymore. For a few weeks already, yogaDNS is also not working anymore with NextDNS configured.
For the windows client, as of today, it won't connect anymore. When I right click the tray icon > enable, it just doesn't nothing. When I mannually restart the nextDNS application, I get the error "getTuntapComponentld: not found component id". When this happens, the status in the tray icon stays at "connecting". I already tried reinstalling it but that gave an error in installing the adapter I think/.
YogaDNS stopped working a few weeks ago. It worked fine before. I setup quad9 dns in my router as a fallback option. Still, YogaDNS chooses this as the option. Even removing quad9 from the router does not solve it.
[01.10 10:42:53] dns.quad9.net - request : type=A, server=149.112.112.112:53, program=svchost.exe
[01.10 10:42:53] dns.quad9.net - process : server=NextDNS (NextDNS, <MyID>), rule=Default
[01.10 10:42:53] dns.quad9.net - reply : type=A, ips=149.112.112.112, 9.9.9.9
I use windows 10 2004 64bit.
Any help is appriciated.
-
I regularly have the same problem. If I right click on nextdns in the taskbar, the top line says "connecting" in the context menu. Exiting and relaunching nextdns does not solve the issue. I figured out restarting my full computer solves the problem. I have to do this every few days to be able to keep using nextdns.
-
Hello, I'm having the same problem since installing the Client, I managed to "solve" it by going to Windows Services (with admin) and restarting the NextDNS service called: "NextDNS DNS53 to DoH proxy". With that automatically the Client connects and the Disable option appears indicating that everything is fine.
I haven't figured out any other way to do this automatically so maybe creating a BAT script to restart the service after a few seconds or minutes after startup will fix the problem, but I haven't tested it yet.