NextDNSService remains running but DoH DNS resolution stops working on Windows 10/11

We have deployed NextDNS on several Windows 10 and Windows 11 computers to test our DNS filtering and site-blocking policies.

After running for some time, I noticed on my own computer that the NextDNS profile displayed the message that the device was no longer using NextDNS. At the same time, no DNS queries had been logged in the NextDNS portal for a while.

The issue is resolved either by rebooting the computer or by manually restarting the NextDNSService service. Interestingly, the service is still shown as Running, but DNS resolution through NextDNS stops working until the service is restarted.

At first, I thought this was isolated to my laptop. However, after checking several other Windows 10 and Windows 11 computers, I found that the same issue occurs quite frequently. In every case, restarting the computer (or restarting the NextDNSService service) restores normal operation.

Additional information:

• NextDNS client version: 3.0.13

• Installed using the MSI installer.

• Using DNS-over-HTTPS (DoH).

• The issue has been observed on computers connected through both Wi-Fi and Ethernet.

• Some affected laptops enter sleep mode, but the problem is not limited to sleep/resume scenarios. For example, it has also occurred on my personal desktop computer, which never enters sleep mode automatically.

Has anyone experienced this behavior before? Is this a known issue with version 3.0.13? Are there any logs or troubleshooting steps that could help determine why the NextDNSService remains running while DNS resolution through NextDNS stops working?