After clearing the logs, new DNS queries stop appearing in the Logs section.
I was able to reproduce this on two different NextDNS profiles:
Create/use a profile — DNS queries appear in the logs normally.
Click Clear Logs.
After that, new queries stop appearing, even though Private DNS / DNS-over-TLS is still working and test.nextdns.io shows status: ok.
Creating a new profile fixes the issue immediately, but if I clear the logs on the new profile, logging stops there as well.
So this seems to be directly related to the Clear Logs function, not to the device, DNS-over-TLS configuration, query limit, or profile settings.
Has anyone else experienced this? Is there a known delay after clearing logs, or could this be a bug?
3 replies
-
I managed to solve the issue.
After using Clear Logs, it seems that the existing DNS-over-TLS connection may continue using the old session/state, and new queries do not appear in the logs immediately.
What worked for me:
Clear the logs in NextDNS.
Change the NextDNS server/storage location.
Force the device to reconnect to the network — on my own phone I used Airplane Mode to completely disconnect and reconnect.
After the network connection and DNS-over-TLS session were re-established, the logs started working normally again.
I also confirmed this with another device that I could not manually reconnect. After its network connection was interrupted/re-established later, its queries started appearing in the logs again.
So in my case, the problem was resolved by forcing a new network/DoT session after clearing the logs.
-
Update: the issue seems to affect not only the Logs section, but also the account query counter.
test.nextdns.ioshows that DNS-over-TLS is working correctly (status: ok) and the correct profile/device is detected.However:
- Normal DNS queries are not appearing in Logs.
- The Free Usage counter is stuck at 50,340 / 300,000 and does not increase at all.
- I tested this on my own phone by enabling the NextDNS Private DNS and opening new websites.
- The issue also occurs with more than one profile.
- DNS resolution itself still works.
This makes me suspect that the problem may be related to query accounting or the account state rather than the device configuration.
Could the account have reached the actual query limit while the UI is showing an incorrect usage value, or is there currently an issue with query accounting/logging?
-
The queries counter is broken for some time now, there are multiple posts about this but no answer yet. The number it get stuck on is different and random apparently and this mean that some will get over the limit and will not see it by looking at the queries numbers.
Content aside
- 18 hrs agoLast active
- 3Replies
- 26Views
-
1
Following
