2

Endpoint Failed (regular)

Hi,

I have been having a very common issue recently, almost daily, often twice daily, and its causing a lot of subsequent issues.

The common thread I see in my ASUS (Merlin OS with NextDNS CLI installed, all up to date as of post) is the following:

 

nextdns[2854]: Endpoint failed: https://dns1.nextdns.io#45.90.....

nextdns[2854]: Endpoint failed: https://dns2.nextdns.io#45.90.....

nextdns[2854]: Endpoint provider failed: &{dns.nextdns.io https://dns.nextdns.io#45.90

nextdns[2854]: parse question: parsing/packing of this section has completed

nextdns[2854]: parse additional: Name: insufficient data for calculated length type

This can go into a bit of a continues stream of errors, causing havoc with individual devices, and causing me to have no internet for a period of time.

The common trend is for this to happen every evening between 21:00 - 00:00, but that's not always the case.

Sadly, I'm not expecting any kind of meaningful response, never mind support, from anyone at NextDNS, but I thought I would post anyway, just to see if anyone else has come across this issue, and possibly found a fix.

I wish I could ignore it and continue with the service, as I have as a premium member for 2 years, but that patience is being tested.

Kindest regards

And happy privacy protecting

15replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Please provide a https://nextdns.io/diag when you get this issue so we can investigate it.

    Like
      • Mark
      • 🤖
      • MarkToon
      • 6 mths ago
      • Reported - view

      NextDNS I was about 10 mins late to the actual issue, but here's a log after the event.

      https://nextdns.io/diag/b612bdf0-07b5-11ed-a9a6-77017d3a7e52

      This was accompanied by slow internet resolving, YouTube videos very, very slow to load etc.

      Not sure what is gained from this diag, it isn't very detailed.

      For what it's worth, I use the following router:

      ASUS GT-AXE11000 - Merlin OS 386.7

      ISP: Virgin Media UK 1Gbps Fibre

      nextdns[2854]: parse question: parsing/packing of this section has completed
      nextdns[2854]: parse additional: Name: insufficient data for calculated length type
      nextdns[2854]: parse question: parsing/packing of this section has completed

      I see these logs so often.

      Like
      • Mark
      • 🤖
      • MarkToon
      • 6 mths ago
      • Reported - view

      NextDNS Any thoughts?

      Like
  • Those errors mean some invalid DNS queries are sent to the CLI. It should be inconsequential. If you have a lot of these, perhaps something is flooding your router port 53 UDP with garbage data.

    Like
  • I am still going through this issue, on a daily basis, and it's really getting my goat now.

    nextdns[2877]: Endpoint provider failed

    Sick of seeing this line.

    I have completely wiped the router, and still, this keeps on happening.

    Like 2
    • Mark  I have the same issue. 😥

      Like 1
      • Jörgen
      • Pro Subscriber ✅
      • Jorgen_A
      • 5 mths ago
      • 1
      • Reported - view

      Mark I would try the following troubleshooting...

      1. Disable Trend Micro AiProtection for a few days. Any difference?!
      2. Uninstall NextDNS CLI and setup DNS with the native support for DoT (DNS-over-TLS) in ASUS Merlin. Any difference?! (This worked great for me)
      3. Use plain-text DNS with the 45.90.28.x and 45.90.30.x in the WAN-section.

      I also had issues with the CLI in ASUS Merlin and gave it up a few months ago. Now using AdGuard DNSProxy with NextDNS doing DoQ/DoT/DNScrypt and not a single DNS-issue for months on my AX86U.

      Like 1
      • Mark
      • 🤖
      • MarkToon
      • 5 mths ago
      • Reported - view

      Jörgen Hi, would you be able to provide more information on the very last option?

      I'm pretty much done with NextDNS CLI, it's crap.

      Like
      • Mark
      • 🤖
      • MarkToon
      • 5 mths ago
      • Reported - view

      M. Sait Yagli Yeah it's never ending, I'm done supporting NextDNS and promoting them to others.

      Like
      • Jörgen
      • Pro Subscriber ✅
      • Jorgen_A
      • 5 mths ago
      • 1
      • Reported - view

      Mark You can check out DNSproxy here: https://github.com/AdguardTeam/dnsproxy

      There is no installation-script so quite a few steps to do, but if you are familiar with ssh/scripting "behind the scene" you can figure it out. If I get the time I might do an installation instruction on my own Github page.

      Do you still have the same issues if you setup DoT with the native support in ASUS Merlin?

      PS. NextDNS is still the best DNS-provider in my opinion, so give them another chance! :-)

      Like 1
      • Mark
      • 🤖
      • MarkToon
      • 5 mths ago
      • Reported - view

      Jörgen If you ever get time to do that instruction sheet on GitHub, ill buy you a beer :) As I'm not too comfortable scripting. 

      The only issue with the DoT setup is the lack of device names coming through, as I really like to monitor individual devices. All I seem to get is my IP.

      Like
      • Jörgen
      • Pro Subscriber ✅
      • Jorgen_A
      • 5 mths ago
      • Reported - view

      Mark I forgot to mention that device-names don't work with DNSproxy, but that's not an issue for me. If something is blocked it's shown within the latest 10 entries in the log and easily found.

      Your issue seems to be the same as I had with the CLI. Suddenly all DOH-queries stopped working for a while and nothing works. I would switch to DoT in ASUS Merlin if I were you...

      Like
  • Aug 31 12:57:48 nextdns[2749]: Endpoint failed: https://dns1.nextdns.io#45.90.28.0,2a07:a8c0::: roundtrip: dial tcp 45.90.28.0:443: connect: network is unreachable
    Aug 31 12:57:48 nextdns[2749]: Endpoint failed: https://dns2.nextdns.io#45.90.30.0,2a07:a8c1::: roundtrip: dial tcp 45.90.30.0:443: connect: network is unreachable

    This is several times a day, come on, give me some service here!! Are there any more reliable endpoints? This is honestly terrible and its causing a lot of issues in our home.

    @NextDNSAdmin

    Like 1
Like2 Follow
  • 2 Likes
  • 5 mths agoLast active
  • 15Replies
  • 225Views
  • 5 Following