1

Lot of disconnections, NextDNS CLI has to be reinstalled every 2 days

I am experiencing a lot of disconnections the last few months .Today I experienced a few of them so I checked my logs. I am suspecting it has something to do with NextDNS.

Every two days I have to install NextDNS CLI again on my Asuswrt-Merlin AC86U Router. It is weird as NextDNS is still working on my network (filtering is working), but the CLI is not responsive as you see in the image below. 

  

Here are the NextDNS Network Diagnostic Tool Results:  https://nextdns.io/diag/56fdc8a0-368b-11ed-a3c4-15a7fcb1a4b7

Here are the logs from Asuswrt-Merlin: 

Sep 17 13:54:26 nextdns[2293]: Connected 194.182.182.199:443 (con=17ms tls=18ms, TCP, TLS13)
Sep 17 13:54:27 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc0125938a8 next ffffffc0126206e0 prev ffffffc0126206e0 rep_entry->list ffffffc0126206e0 next ffffffc0125938a8 prev ffffffc0125938a8
Sep 17 13:56:41 nextdns[2293]: Connected 194.182.182.199:443 (con=16ms tls=19ms, TCP, TLS13)
Sep 17 13:56:41 nextdns[2293]: Connected 194.182.182.199:443 (con=14ms tls=393ms, TCP, TLS13)
Sep 17 13:56:41 nextdns[2293]: Switching endpoint: https://dns.nextdns.io#194.182.182.199,2a04:c42:e00:8370:4e3:1aff:fe00:295,217.146.30.7,2a00:11c0:3:949::5
Sep 17 13:59:10 nextdns[2293]: Connected 194.182.182.199:443 (con=27ms tls=25ms, TCP, TLS13)
Sep 17 13:59:47 nextdns[2293]: Connected 194.182.182.199:443 (con=11ms tls=18ms, TCP, TLS13)
Sep 17 13:59:47 nextdns[2293]: parse question: parsing/packing of this section has completed
Sep 17 13:59:47 nextdns[2293]: parse question: parsing/packing of this section has completed
Sep 17 13:59:47 nextdns[2293]: parse additional: Name: insufficient data for calculated length type
Sep 17 13:59:47 nextdns[2293]: Query 127.0.0.1 UDP A google.com. (qry=51/res=12) cache fallback HTTP/2.0: doh resolve: error code: 400
Sep 17 13:59:51 nextdns[2293]: parse additional: Name: insufficient data for calculated length type
Sep 17 14:00:05 nextdns[2293]: parse question: parsing/packing of this section has completed
Sep 17 14:00:05 nextdns[2293]: parse question: parsing/packing of this section has completed
Sep 17 14:00:05 nextdns[2293]: parse additional: Name: insufficient data for calculated length type
Sep 17 15:02:08 nextdns[17661]: Connected 194.182.182.199:443 (con=12ms tls=19ms, TCP, TLS13)
Sep 17 15:03:41 nextdns[17661]: Connected 194.182.182.199:443 (con=13ms tls=18ms, TCP, TLS13)
Sep 17 15:05:20 nextdns[17661]: Connected 194.182.182.199:443 (con=15ms tls=25ms, TCP, TLS13)
Sep 17 15:09:53 nextdns[17661]: Connected 194.182.182.199:443 (con=13ms tls=20ms, TCP, TLS13)
Sep 17 15:12:59 nextdns[17661]: Connected 194.182.182.199:443 (con=14ms tls=19ms, TCP, TLS13)
Sep 17 15:15:03 nextdns[17661]: Connected 194.182.182.199:443 (con=12ms tls=18ms, TCP, TLS13)
Sep 17 15:16:05 nextdns[17661]: Connected 194.182.182.199:443 (con=16ms tls=34ms, TCP, TLS13)
Sep 17 15:17:51 nextdns[17661]: Connected 194.182.182.199:443 (con=0ms tls=0ms, TCP, )
Sep 17 15:20:11 nextdns[17661]: Connected 194.182.182.199:443 (con=11ms tls=22ms, TCP, TLS13)
Sep 17 15:21:12 nextdns[17661]: Connected 194.182.182.199:443 (con=19ms tls=23ms, TCP, TLS13)
Sep 17 15:22:00 nextdns[17661]: Connected 194.182.182.199:443 (con=16ms tls=25ms, TCP, TLS13)
Sep 17 15:23:19 nextdns[17661]: Connected 194.182.182.199:443 (con=11ms tls=19ms, TCP, TLS13)
Sep 17 14:44:05 nextdns[17661]: Connected 45.90.28.0:443 (con=21ms tls=461ms, TCP, TLS13)
Sep 17 14:44:06 nextdns[17661]: Connected 194.182.182.199:443 (con=6ms tls=476ms, TCP, TLS13)
Sep 17 14:44:06 nextdns[17661]: Switching endpoint: https://dns.nextdns.io#217.146.30.7,2a00:11c0:3:949::5,194.182.182.199,2a04:c42:e00:8370:4e3:1aff:fe00:295

Are these LOGS normal ? 
Why is it switching endpoints so often ?

Here are the nextdns logs:

Sep 17 11:56:39 nextdns[2293]: Connected 194.182.182.199:443 (con=14ms tls=409ms, TCP, TLS13)
Sep 17 11:56:39 nextdns[2293]: Switching endpoint: https://dns.nextdns.io#217.146.30.7,2a00:11c0:3:949::5,194.182.182.199,2a04:c42:e00:8370:4e3:1aff:fe00:295
Sep 17 12:52:58 nextdns[2293]: Connected 194.182.182.199:443 (con=16ms tls=25ms, TCP, TLS13)
Sep 17 12:53:45 nextdns[2293]: Connected 194.182.182.199:443 (con=18ms tls=24ms, TCP, TLS13)
Sep 17 12:56:40 nextdns[2293]: Connected 194.182.182.199:443 (con=14ms tls=20ms, TCP, TLS13)
Sep 17 13:05:43 nextdns[2293]: Connected 194.182.182.199:443 (con=17ms tls=24ms, TCP, TLS13)
Sep 17 13:16:15 nextdns[2293]: Connected 194.182.182.199:443 (con=14ms tls=24ms, TCP, TLS13)
Sep 17 13:17:13 nextdns[2293]: Connected 194.182.182.199:443 (con=18ms tls=20ms, TCP, TLS13)
Sep 17 13:17:34 nextdns[2293]: parse question: parsing/packing of this section has completed
Sep 17 13:17:34 nextdns[2293]: parse question: parsing/packing of this section has completed
Sep 17 13:17:34 nextdns[2293]: parse additional: Name: insufficient data for calculated length type
Sep 17 13:33:15 nextdns[2293]: Connected 194.182.182.199:443 (con=11ms tls=18ms, TCP, TLS13)
Sep 17 13:43:07 nextdns[2293]: Connected 194.182.182.199:443 (con=19ms tls=21ms, TCP, TLS13)
Sep 17 13:43:07 nextdns[2293]: parse question: parsing/packing of this section has completed
Sep 17 13:43:07 nextdns[2293]: parse question: parsing/packing of this section has completed
Sep 17 13:43:07 nextdns[2293]: parse additional: Name: insufficient data for calculated length type
Sep 17 13:44:12 nextdns[2293]: Connected 194.182.182.199:443 (con=16ms tls=19ms, TCP, TLS13)
Sep 17 13:44:42 nextdns[2293]: parse question: parsing/packing of this section has completed
Sep 17 13:44:42 nextdns[2293]: parse question: parsing/packing of this section has completed
Sep 17 13:44:42 nextdns[2293]: parse additional: Name: insufficient data for calculated length type
Sep 17 13:45:04 nextdns[2293]: parse question: parsing/packing of this section has completed
Sep 17 13:45:04 nextdns[2293]: parse question: parsing/packing of this section has completed
Sep 17 13:45:04 nextdns[2293]: parse additional: Name: insufficient data for calculated length type
Sep 17 13:46:18 nextdns[2293]: Connected 194.182.182.199:443 (con=18ms tls=18ms, TCP, TLS13)
Sep 17 13:48:22 nextdns[2293]: Connected 194.182.182.199:443 (con=15ms tls=20ms, TCP, TLS13)
Sep 17 13:49:23 nextdns[2293]: Connected 194.182.182.199:443 (con=17ms tls=20ms, TCP, TLS13)
Sep 17 13:53:45 nextdns[2293]: Connected 194.182.182.199:443 (con=16ms tls=26ms, TCP, TLS13)
Sep 17 13:54:26 nextdns[2293]: Connected 194.182.182.199:443 (con=17ms tls=18ms, TCP, TLS13)
Sep 17 13:56:41 nextdns[2293]: Connected 194.182.182.199:443 (con=16ms tls=19ms, TCP, TLS13)
Sep 17 13:56:41 nextdns[2293]: Connected 194.182.182.199:443 (con=14ms tls=393ms, TCP, TLS13)
Sep 17 13:56:41 nextdns[2293]: Switching endpoint: https://dns.nextdns.io#194.182.182.199,2a04:c42:e00:8370:4e3:1aff:fe00:295,217.146.30.7,2a00:11c0:3:949::5
Sep 17 13:59:10 nextdns[2293]: Connected 194.182.182.199:443 (con=27ms tls=25ms, TCP, TLS13)
Sep 17 13:59:47 nextdns[2293]: Connected 194.182.182.199:443 (con=11ms tls=18ms, TCP, TLS13)
Sep 17 13:59:47 nextdns[2293]: parse question: parsing/packing of this section has completed
Sep 17 13:59:47 nextdns[2293]: parse question: parsing/packing of this section has completed
Sep 17 13:59:47 nextdns[2293]: parse additional: Name: insufficient data for calculated length type
Sep 17 13:59:47 nextdns[2293]: Query 127.0.0.1 UDP A google.com. (qry=51/res=12) cache fallback HTTP/2.0: doh resolve: error code: 400
Sep 17 13:59:51 nextdns[2293]: parse additional: Name: insufficient data for calculated length type
Sep 17 14:00:05 nextdns[2293]: parse question: parsing/packing of this section has completed
Sep 17 14:00:05 nextdns[2293]: parse question: parsing/packing of this section has completed
Sep 17 14:00:05 nextdns[2293]: parse additional: Name: insufficient data for calculated length type
Sep 17 14:09:06 nextdns[2293]: Connected 194.182.182.199:443 (con=11ms tls=24ms, TCP, TLS13)
Sep 17 14:10:00 nextdns[2293]: Connected 194.182.182.199:443 (con=12ms tls=20ms, TCP, TLS13)
Sep 17 14:10:49 nextdns[2293]: Connected 194.182.182.199:443 (con=15ms tls=25ms, TCP, TLS13)
Sep 17 14:15:33 nextdns[2293]: Connected 194.182.182.199:443 (con=13ms tls=20ms, TCP, TLS13)
Sep 17 14:16:07 nextdns[2293]: Connected 194.182.182.199:443 (con=16ms tls=20ms, TCP, TLS13)
Sep 17 14:18:22 nextdns[2293]: Connected 194.182.182.199:443 (con=15ms tls=19ms, TCP, TLS13)
Sep 17 14:20:05 nextdns[2293]: Connected 194.182.182.199:443 (con=0ms tls=0ms, TCP, )
Sep 17 14:30:05 nextdns[2293]: Connected 194.182.182.199:443 (con=15ms tls=27ms, TCP, TLS13)
Sep 17 14:31:07 nextdns[2293]: Connected 194.182.182.199:443 (con=13ms tls=0ms, TCP, )
Sep 17 14:35:15 nextdns[2293]: Connected 194.182.182.199:443 (con=17ms tls=18ms, TCP, TLS13)
Sep 17 14:39:40 nextdns[2293]: Connected 194.182.182.199:443 (con=12ms tls=18ms, TCP, TLS13)
Sep 17 14:43:56 nextdns[2293]: Received signal: terminated
Sep 17 14:43:56 nextdns[2293]: Stopping NextDNS 1.37.11/linux
Sep 17 14:43:56 nextdns[2293]: Restore router settings
Sep 17 14:43:56 nextdns[2293]: NextDNS 1.37.11/linux stopped
Sep 17 14:43:57 nextdns[17661]: Starting NextDNS 1.37.11/linux on 127.0.0.1:5342
Sep 17 14:43:57 nextdns[17661]: Listening on TCP/127.0.0.1:5342
Sep 17 14:43:57 nextdns[17661]: Starting mDNS discovery
Sep 17 14:43:57 nextdns[17661]: Listening on UDP/127.0.0.1:5342
Sep 17 14:44:02 nextdns[17661]: Setting up router
Sep 17 14:44:05 nextdns[17661]: Connected 45.90.28.0:443 (con=21ms tls=461ms, TCP, TLS13)
Sep 17 14:44:06 nextdns[17661]: Connected 194.182.182.199:443 (con=6ms tls=476ms, TCP, TLS13)
Sep 17 14:44:06 nextdns[17661]: Switching endpoint: https://dns.nextdns.io#217.146.30.7,2a00:11c0:3:949::5,194.182.182.199,2a04:c42:e00:8370:4e3:1aff:fe00:295
Sep 17 14:50:53 nextdns[17661]: Connected 194.182.182.199:443 (con=12ms tls=22ms, TCP, TLS13)
Sep 17 14:58:02 nextdns[17661]: Connected 194.182.182.199:443 (con=17ms tls=21ms, TCP, TLS13)
Sep 17 14:59:04 nextdns[17661]: Connected 194.182.182.199:443 (con=18ms tls=18ms, TCP, TLS13)
Sep 17 15:02:08 nextdns[17661]: Connected 194.182.182.199:443 (con=12ms tls=19ms, TCP, TLS13)
Sep 17 15:03:41 nextdns[17661]: Connected 194.182.182.199:443 (con=13ms tls=18ms, TCP, TLS13)

11 replies

null
    • Software Developer
    • Devid
    • 2 yrs ago
    • Reported - view

    I have heard that this is caused by some faulty Client: 


    Sep 17 13:45:04 nextdns[2293]: parse additional: Name: insufficient data for calculated length type

    How can I find which client is causing this problem ?

      • Chess_McKinney
      • 2 yrs ago
      • Reported - view

      Devid If you find an answer, I'd like to know what is causing the parse error.  Have it daily, sometimes several times on an EdgeRouter.

    • Raspberry_Beam
    • 2 yrs ago
    • Reported - view

    put the issue on their github https://github.com/nextdns

    • NextDNs
    • 2 yrs ago
    • Reported - view

    When you say you experience disconnection, does it result in inability to resolve hostnames or your question is just about the logs?

      • Software Developer
      • Devid
      • 2 yrs ago
      • Reported - view

      NextDNS the first question would be, why do I have to reinstall every two days the NextDNS CLI. As seen in the image nextdns is there, but when I call I get nextdns: not found. 

      The other question is related to the disconnections. I am not 100% sure, but I think it has something to do with NextDNS that is why I posted the logs. 

      • NextDNs
      • 2 yrs ago
      • Reported - view

      Devid on merlin, when you upgrade or restart the router, nextdns may disapear from the path. It is still installed but not in the path. You should always be able to execute it by using its full path: /jffs/nextdns/nextdns

      • Software Developer
      • Devid
      • 2 yrs ago
      • Reported - view

      NextDNS Ok I will try this in few days and report back. 

      • Michael_Bierman
      • 2 yrs ago
      • Reported - view

      NextDNS I took your advice and used the full path to NextDNS and I still see NextDNS report it is down several times a day. Either I’ve misconfigured something or there seems to be a bug. What can I do to fix my config or give you information to identify and fix the issue?

    • Michael_Bierman
    • 2 yrs ago
    • Reported - view

    I see this too. I check the status with cron every 5 min and several times a day it says nextdns is not running so I restart it.  I wrote some scripts for install, uninstall, and restarting. 
     

    https://github.com/mbierman/Firewalla-NextDNS-CLI-install

    • Michael_Bierman
    • 2 yrs ago
    • Reported - view

    To give an idea of the probelem I'm seeing here are some logs for the last few days where a cronjob tests every 5 minutes.  

    Sun Sep 18 07:00:02 PDT 2022 nextdns failed try:1
Sun Sep 18 07:00:02 PDT 2022 nextdns failed try:2
Sun Sep 18 07:10:02 PDT 2022 nextdns failed try:1
Sun Sep 18 07:30:02 PDT 2022 nextdns failed try:1
Sun Sep 18 07:35:01 PDT 2022 nextdns failed try:1
Sun Sep 18 09:10:02 PDT 2022 nextdns failed try:1
Sun Sep 18 09:20:02 PDT 2022 nextdns failed try:1
Sun Sep 18 09:35:01 PDT 2022 nextdns failed try:1
Sun Sep 18 10:15:01 PDT 2022 nextdns failed try:1
Sun Sep 18 13:00:02 PDT 2022 nextdns failed try:1
Sun Sep 18 14:00:02 PDT 2022 nextdns failed try:1
Sun Sep 18 14:00:02 PDT 2022 nextdns failed try:2
Sun Sep 18 14:00:02 PDT 2022 nextdns failed try:3
Sun Sep 18 16:10:01 PDT 2022 nextdns failed try:1
Sun Sep 18 16:50:01 PDT 2022 nextdns failed try:1
Sun Sep 18 18:55:01 PDT 2022 nextdns failed try:1
Sun Sep 18 20:15:01 PDT 2022 nextdns failed try:1
Sun Sep 18 20:20:02 PDT 2022 nextdns failed try:1
Sun Sep 18 21:10:01 PDT 2022 nextdns failed try:1
Sun Sep 18 21:35:01 PDT 2022 nextdns failed try:1
Sun Sep 18 22:55:01 PDT 2022 nextdns failed try:1
Sun Sep 18 23:10:02 PDT 2022 nextdns failed try:1
Mon Sep 19 00:00:02 PDT 2022 nextdns failed try:1
Mon Sep 19 00:50:01 PDT 2022 nextdns failed try:1
Mon Sep 19 02:30:01 PDT 2022 nextdns failed try:1
Mon Sep 19 03:15:01 PDT 2022 nextdns failed try:1
Mon Sep 19 03:50:02 PDT 2022 nextdns failed try:1
Mon Sep 19 04:30:02 PDT 2022 nextdns failed try:1
Mon Sep 19 04:35:01 PDT 2022 nextdns failed try:1
Mon Sep 19 04:40:01 PDT 2022 nextdns failed try:1
Mon Sep 19 05:20:02 PDT 2022 nextdns failed try:1
Mon Sep 19 05:55:01 PDT 2022 nextdns failed try:1
Mon Sep 19 06:05:01 PDT 2022 nextdns failed try:1
Mon Sep 19 07:05:02 PDT 2022 nextdns failed try:1
Mon Sep 19 08:35:02 PDT 2022 nextdns failed try:1
Mon Sep 19 08:35:02 PDT 2022 nextdns failed try:2
Mon Sep 19 09:40:01 PDT 2022 nextdns failed try:1
Mon Sep 19 09:45:02 PDT 2022 nextdns failed try:1
Mon Sep 19 10:30:02 PDT 2022 nextdns failed try:1
Mon Sep 19 10:35:01 PDT 2022 nextdns failed try:1
Mon Sep 19 10:55:01 PDT 2022 nextdns failed try:1

    Note each time it fails  

    sudo /usr/bin/nextdns restart

    runs and the test goes again and usually passes. 

    • Michael_Bierman
    • 2 yrs ago
    • Reported - view

    I’m fairly disappointed that @nextdns hasn’t replied to this thread. Having DNS a service fail multiple times a day is one of the more consequential problems  can imagine with a DNS provider. 

Login to reply

Content aside

  • 1 Likes
  • 2 yrs agoLast active
  • 11Replies
  • 335Views
  • 6 Following