0

Log errors "doh resolve: context deadline exceeded"

I have recently started to see groups of entries like this quite often in logs. Any clue what's happening?!

May  6 08:01:36 nextdns[2318]: Query <client ip> UDP A clients3.google.com. (qry=70/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
May  6 08:01:37 nextdns[2318]: Query <client ip> UDP A clients3.google.com. (qry=70/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
May  6 08:01:38 nextdns[2318]: Query <client ip> UDP A clients3.google.com. (qry=70/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
May  6 08:01:39 nextdns[2318]: Query <client ip> UDP A clients3.google.com. (qry=70/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
May  6 08:01:40 nextdns[2318]: Query <client ip> UDP A clients3.google.com. (qry=70/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded

Platform: ASUS Merlin
CLI: 1.37.11

5 replies

null
    • Pro Subscriber ✅
    • Jorgen_A
    • 3 yrs ago
    • Reported - view

    Did some digging myself and seems to be the UltraLow PoP "ipv4-edis-cph-1.edge.nextdns.io" on 192.36.27.86 that don't perform good. Every time the CLI switches to it, these errors begins and it switches back to 188.172.192.71 but after a while it's back again.

    Two samples that occurs all the time now: 

    May  7 12:01:45 nextdns[2349]: Query x.x.x.x UDP A play.googleapis.com. (qry=70/res=12) 5001ms HTTP/2.0: doh resolve: context deadline exceeded
May  7 12:01:45 nextdns[2349]: Query x.x.x.x UDP AAAA play.googleapis.com. (qry=70/res=12) 5000ms HTTP/2.0: doh resolve: context deadline exceeded
    May  7 12:42:34 nextdns[2349]: Connected 192.36.27.86:443 (con=3ms tls=486ms, TCP, TLS13)
May  7 12:42:34 nextdns[2349]: Switching endpoint: https://dns.nextdns.io#192.36.27.86,2a03:f80:45:192:36:27:86:1,188.172.192.71,2a00:11c0:2e:350::3

    My route to 192.36.27.86 seems OK (skipped the first 4 hops due to privacy) 

      5     3 ms     3 ms     3 ms  m-b-peer1-link.se.telia.net [81.228.86.13]
  6     4 ms     3 ms     3 ms  kbn-b1-link.ip.twelve99.net [62.115.123.158]
  7     6 ms     5 ms     6 ms  kbn-bb2-link.ip.twelve99.net [62.115.138.112]
  8     4 ms     4 ms     *     kbn-b4-link.ip.twelve99.net [62.115.136.231]
  9     4 ms     4 ms     4 ms  m247-ic325899-kbn-b3.ip.twelve99-cust.net [213.248.89.119]
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     5 ms     4 ms     4 ms  dns.nextdns.io [192.36.27.86]
    • Pro Subscriber ✅
    • Jorgen_A
    • 3 yrs ago
    • Reported - view

    Please @nextdns team.  Any help would be really appreciated...  🙏

    The DNS-drops happens every 30 mins (a few minutes past the hour/half hour). Example between 08:01-08:03, 08:31-08:33, 09:01-09:03, 09:31-09:33 and so on. This is too regular to be a coincidence.

    Can you see something on the serverlogs on your side?! I don't have any drops in connection and don't have any jobs running every 30 mins. Had several ongoing ping's to check connectivity and all is fine, except DNS-queries not being resolved/responded to.

    Any recent updates on the server-software the past few weeks that can be the source or some scheduled task running every 30 mins making a short interupt in the service?! 

    May 25 08:32:03 nextdns[22759]: Query <Redacted IP> UDP A <Redacted website>. (qry=79/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
May 25 08:32:04 nextdns[22759]: Query <Redacted IP> UDP A <Redacted website>. (qry=79/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
---
May 25 09:01:35 nextdns[22759]: Query <Redacted IP> UDP 65 <Redacted website>. (qry=64/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
May 25 09:01:35 nextdns[22759]: Query <Redacted IP> UDP A <Redacted website>. (qry=64/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
---
May 25 09:33:03 nextdns[22759]: Query <Redacted IP> UDP A <Redacted website>. (qry=77/res=12) 2000ms : doh resolve: context deadline exceeded
May 25 09:33:03 nextdns[22759]: Query <Redacted IP> UDP A <Redacted website>. (qry=77/res=12) 2001ms : doh resolve: context deadline exceeded
--
May 25 11:31:36 nextdns[22759]: Query <Redacted IP> UDP AAAA <Redacted website>. (qry=66/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
May 25 11:31:36 nextdns[22759]: Query <Redacted IP> UDP A <Redacted website>. (qry=66/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
---
May 25 13:01:52 nextdns[22759]: Query <Redacted IP> UDP A <Redacted website>. (qry=70/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
May 25 13:01:52 nextdns[22759]: Query <Redacted IP> UDP A <Redacted website>. (qry=70/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
---
May 25 14:32:27 nextdns[22759]: Query <Redacted IP> UDP A <Redacted website>. (qry=80/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
May 25 14:32:28 nextdns[22759]: Query <Redacted IP> UDP A <Redacted website>. (qry=80/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
---
May 25 15:02:21 nextdns[22759]: Query <Redacted IP> UDP A <Redacted website>. (qry=66/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
May 25 15:02:31 nextdns[22759]: Query <Redacted IP> UDP A <Redacted website>. (qry=83/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
---
May 25 15:32:04 nextdns[22759]: Query <Redacted IP> UDP A <Redacted website>. (qry=67/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
May 25 15:32:04 nextdns[22759]: Query <Redacted IP> UDP AAAA <Redacted website>. (qry=67/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
---
May 25 16:02:20 nextdns[22759]: Query <Redacted IP> UDP A <Redacted website>. (qry=74/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
May 25 16:02:20 nextdns[22759]: Query <Redacted IP> UDP A <Redacted website>. (qry=72/res=12) cache fallback HTTP/2.0: doh resolve: context deadline exceeded
      • Jaka
      • 2 yrs ago
      • Reported - view

      Jörgen after 5month no answer 

      • Pro Subscriber ✅
      • Jorgen_A
      • 2 yrs ago
      • Reported - view

      Jaka I gave up using the CLI since I couldn't make it rock-solid. I'm using DNSProxy now (doing DoQ/DoH3/DoT) and not a single issue for months.

      Happy I could stick with NextDNS only using another technical solution.

    • Jaka
    • 2 yrs ago
    • Reported - view

    mine

Login to reply

Content aside

  • 2 yrs agoLast active
  • 5Replies
  • 422Views
  • 3 Following