NextDNS Client Stops Enforcing After Some Time + YogaDNS Does Not Select Lowest Latency Resolver

Hello,

I am facing two separate issues related to using NextDNS on Windows.

The NextDNS Windows Client remains running and appears “Enabled”, but after some time all DNS queries stop going through NextDNS. Filtering and logs disappear on the dashboard, and DNS resolution starts going through ISP’s resolver instead.

The only temporary fix is: disable and enable

inside the NextDNS Client. This restores functionality for a while, but the problem returns after some time again.

This behavior strongly suggests that the client is losing enforcement even though the UI shows “Enabled”.

----------------------------------------------------------------------------------------------------------

Issue 2 — YogaDNS Does Not Select Lowest Latency Resolver

If I uninstall the NextDNS Client and use YogaDNS alone with NextDNS DoH endpoints:

• YogaDNS does not consistently select the lowest latency NextDNS endpoint.

• Even with “Use Ultra-Low Latency” enabled, it often chooses a higher-latency server.

• As a result, DNS response times become noticeably worse.

Expected behavior: YogaDNS should automatically use the ULTRA-LOW or lowest-latency NextDNS endpoint.

Actual behavior: It does not.

• Windows 11 (updated)

• NextDNS Windows Client (latest stable)

• YogaDNS (latest stable)

• No VPN / No proxy

What I Tried

• Clean reinstall of NextDNS Client

• Clean reinstall of YogaDNS

• Disabled Windows DNS caching

• Manually pinned multiple NextDNS DoH endpoints in YogaDNS

• Tested different networks and ISPs

• Verified no firewall or filter interference

Request

1. For the Client Issue:
   Is there a known condition where the NextDNS Windows Client shows “Enabled” but silently stops enforcing? If yes, is there a workaround or a fix planned?

2. For the YogaDNS Issue:
   Is there an official recommended configuration for reliable ultra-low latency endpoint selection when using YogaDNS with NextDNS?

If these two components are not intended to be used together, please clarify the supported configuration path for strict no-fallback DNS enforcement.

Thank you.