service unreliable - not filtering - long query times - setup page showing 'unconfigured'

I am experiencing the same problems.

From what I can tell, it started having issues six days ago:

syslog.7.gz:Mar 25 20:55:36 nextdns[1040]: Query 127.0.0.1 UDP A dns.nextdns.io.lan. (qry=36/res=12) 5000ms : doh resolve: context deadline exceeded
syslog.7.gz:Mar 25 20:55:39  nextdns[1040]: Query 127.0.0.1 UDP A www.theregister.com.lan. (qry=41/res=12) 5000ms : doh resolve: context deadline exceeded
syslog.7.gz:Mar 25 20:55:40 nextdns[1040]: Query 127.0.0.1 UDP A www.theregister.com. (qry=37/res=12) cached HTTP/2.0: doh resolve: context deadline exceeded

That's PDT timezone.

This is with nextdns 1.11.0 installed and running.

And appears to be getting worse:

zgrep -i "context deadline exceeded" syslog* | awk '{print $1, $2}' | uniq -c | sort -n
      4 syslog.2.gz:Mar 31
     37 syslog.3.gz:Mar 29
     78 syslog.5.gz:Mar 27
    154 syslog:Apr 1
    454 syslog.7.gz:Mar 25
   2259 syslog.1:Mar 31
   2878 syslog.2.gz:Mar 30

Oh yeah - didn't realise it was borked this badly - maybe my decision about continuing to pay has been made for me seeing as the service is not exactly robust:

  ~ ❯ journalctl | grep "context deadline exceeded" | awk '{print $1, $2}' | uniq -c | sort -n                       thalamus@nas
      1 Mar 27
      2 Mar 16
      2 Mar 31
      3 Mar 22
      9 Mar 25
     23 Mar 19
    135 Mar 17
    374 Apr 01
   1385 Mar 24
   1422 Mar 23
   2616 Mar 29
   2994 Mar 26
  ~ ❯

i had the same issues as original poster