1

doh resolve: context deadline exceeded

Hi  Team support

Testing nextdns since yesterday
I do enjoy this project

Firs of all a great congrats for this nice job

 

So,
Yesterday I decide to install by the Debian Way (no usage of sudo)

As root :

--

wget -qO - https://nextdns.io/repo.gpg | apt-key add -
echo "deb https://nextdns.io/repo/deb stable main" | tee /etc/apt/sources.list.d/nextdns.list
apt install apt-transport-https
apt update
apt install nextdns

--

 

Everything worked fine
and I played with the interface https://my.nextdns.io/ID/setup

to discover all features
 

Nice

This morning, after booted the computer
back to have a look to the interface https://my.nextdns.io/ID/setup

But it seem I a'm not detected as connected to nextDNS

nextdns log tell me :

--
févr. 07 13:49:49 debian1 nextdns[627]: Connected 45.90.28.0:443 (con=22ms tls=320ms,  TLS13)
févr. 07 13:49:49 debian1 nextdns[627]: Switching endpoint: https://dns1.nextdns.io#45.90.28.0,2a07:a8c0::
févr. 07 13:49:49 debian1 nextdns[627]: Query 127.0.0.1 UDP AAAA debian1. (qry=25/res=12) 5339ms : doh resolve: context deadline exceeded

--

Restarting the service with   the command :  nextdns restart
OK

Now the portal tells me
"Perfect this computer use nextDNS with this config"


This time, nextdns log tell me :

--
févr. 07 14:07:43 debian1 nextdns[627]: Received signal: terminated
févr. 07 14:07:43 debian1 systemd[1]: Stopping NextDNS DNS53 to DoH proxy....
févr. 07 14:07:43 debian1 nextdns[627]: Stopping NextDNS 1.10.1/linux
févr. 07 14:07:43 debian1 nextdns[627]: Deactivating
févr. 07 14:07:43 debian1 nextdns[627]: NextDNS 1.10.1/linux stopped
févr. 07 14:07:43 debian1 systemd[1]: nextdns.service: Succeeded.
févr. 07 14:07:43 debian1 systemd[1]: Stopped NextDNS DNS53 to DoH proxy..
févr. 07 14:07:43 debian1 systemd[1]: Started NextDNS DNS53 to DoH proxy..
févr. 07 14:07:43 debian1 nextdns[2635]: Starting NextDNS 1.10.1/linux on localhost:53
févr. 07 14:07:43 debian1 nextdns[2635]: Listening on TCP/[::1]:53
févr. 07 14:07:43 debian1 nextdns[2635]: Listening on UDP/127.0.0.1:53
févr. 07 14:07:43 debian1 nextdns[2635]: Listening on TCP/127.0.0.1:53
févr. 07 14:07:43 debian1 nextdns[2635]: Listening on UDP/[::1]:53
févr. 07 14:07:47 debian1 nextdns[2635]: Connected 45.90.28.0:443 (con=27ms tls=101ms, TLS13)
févr. 07 14:07:48 debian1 nextdns[2635]: Connected 37.252.225.79:443 (con=28ms tls=187ms, TLS13)
févr. 07 14:07:48 debian1 nextdns[2635]: Switching endpoint: https://dns.nextdns.io.#37.252.225.79,2a00:11c0:2:998::3,193.168.204.73,2a0e:9900:0:1::1:2
févr. 07 14:07:48 debian1 nextdns[2635]: Activating

--

 

Rebooting the computer give me same behavior :

- doh resolve: context deadline exceeded

- Restart the service : nextdns restart

- Back to normal

 

Is it a bug or did i miss something ?

Wait for your answer

Regards

 

--

Context

    Version: nextdns version 1.10.1
    Platform : Debian Testing/sid (all updated)

1 reply

null
    • Rodrigo_Roberti
    • 3 yrs ago
    • Reported - view

    Hi @jca...

    I have the some problem, but using NextDNS on OpenWRT...

    When I install and configure, all works fine for sometime... After, I see errors on OpenWRT´s log with "context deadline exceeded"... 

    I open the topic located in => NextDNS stops working after some time it has been configured... - Discussions - NextDNS Help Center with screenshots to discuss the problem, but we still haven't come to any conclusions.

    I don´t know if the problem is caused by OpenWRT´s version (21.02.0) (today I will update to 21.02.1 for new tests), don´t Know if the problem is caused by my ISP (Claro - Brazil), etc...  I know that when I install e configure NextDNS first time, all works very well, but, after some time, NextDNS stops work anf the message can see on logs... 

    Strange is that here, in my house, I use other ISP (Vivo - Brazil) and here, I using the Mitrastar HGU and the unique confiuguration that it accepts, is to manually point the DNS servers... it is not possible to install anything on this modem or check much in the logs (limited to the extreme), but the symptoms are exactly the same... when pointing the servers, it works normally for some time and then to resolutions...

Content aside

  • 1 Likes
  • 3 yrs agoLast active
  • 1Replies
  • 408Views
  • 2 Following