1

Reoccurring Timeouts

I was so excited about this service until I started using it. Maybe it is my end, but I am having ZERO issues with Google. My config is the full version of YogaDNS with NextDNS (paid account) as my primary and Google as secondary. 

At least once a day, queries to NextDNS time out. The idea is excellent, but the implementation is wanting. Even their own lookups time out. (Sample of the log belog)

Am I alone? There seems to be no easy way to get support from NextDNS.

I would love to love the service, but I am close to just accepting it isn't ready for primetime.

-0-

[10.23 17:24:05] carfax-img.vast.com - request timeout : server=NextDNS
[10.23 17:24:05] carfax-img.vast.com - request timeout : server=NextDNS
[10.23 17:24:05] marketplaceassets.azureedge.net - request timeout : server=NextDNS
[10.23 17:24:05] marketplaceassets.azureedge.net - request timeout : server=NextDNS
[10.23 17:24:05] carfax-img.vast.com - request timeout : server=NextDNS
[10.23 17:24:05] carfax-img.vast.com - request timeout : server=NextDNS
[10.23 17:24:05] marketplaceassets.azureedge.net - request timeout : server=NextDNS
[10.23 17:24:05] marketplaceassets.azureedge.net - request timeout : server=NextDNS
[10.23 17:24:05] carfax-img.vast.com - request timeout : server=NextDNS
[10.23 17:24:05] carfax-img.vast.com - request timeout : server=NextDNS
[10.23 17:24:05] marketplaceassets.azureedge.net - request timeout : server=NextDNS
[10.23 17:24:05] marketplaceassets.azureedge.net - request timeout : server=NextDNS
[10.23 17:24:06] DnsCrypt log: Get https://yoga.dns.nextdns.io/bbda68/RCGHQ-XfjuBR3ee?dns=yv4BAAABAAAAAAABAAACAAEAACkQAAAAAAAAFAAMABBP7Z2fGNSC3wBpiAUnSPDQ: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
[10.23 17:24:06] yoga.dns.nextdns.io - resolve server hostname through itself
[10.23 17:24:06] yoga.dns.nextdns.io - resolve server hostname through itself
[10.23 17:24:06] yoga.dns.nextdns.io - resolve server hostname through itself
[10.23 17:24:06] yoga.dns.nextdns.io - resolve server hostname through itself
[10.23 17:24:06] yoga.dns.nextdns.io - resolve server hostname through itself
[10.23 17:24:06] yoga.dns.nextdns.io - resolve server hostname through itself
[10.23 17:24:07] api.nextdns.io - request timeout : server=NextDNS
[10.23 17:24:07] api.nextdns.io - request timeout : server=NextDNS
[10.23 17:24:07] api.nextdns.io - request timeout : server=NextDNS
[10.23 17:24:07] api.nextdns.io - request timeout : server=NextDNS
[10.23 17:24:08] api.nextdns.io - process : server=NextDNS (NextDNS), rule=NextDNS
[10.23 17:24:08] api.nextdns.io - process : server=NextDNS (NextDNS), rule=NextDNS
[10.23 17:24:08] api.nextdns.io - process : server=NextDNS (NextDNS), rule=NextDNS
[10.23 17:24:09] default._dante-ddm-d._udp - process : server=NextDNS (NextDNS), rule=NextDNS
[10.23 17:24:09] api.nextdns.io - request timeout : server=NextDNS
[10.23 17:24:09] api.nextdns.io - request timeout : server=NextDNS
[10.23 17:24:09] yoga.dns.nextdns.io - request timeout : server=NextDNS
[10.23 17:24:09] yoga.dns.nextdns.io - request timeout : server=NextDNS
[10.23 17:24:09] yoga.dns.nextdns.io - request timeout : server=NextDNS
[10.23 17:24:09] yoga.dns.nextdns.io - request timeout : server=NextDNS
[10.23 17:24:09] yoga.dns.nextdns.io - request timeout : server=NextDNS
[10.23 17:24:09] yoga.dns.nextdns.io - request timeout : server=NextDNS
[10.23 17:24:09] yoga.dns.nextdns.io - request timeout : server=NextDNS
[10.23 17:24:09] yoga.dns.nextdns.io - request timeout : server=NextDNS
 

21 replies

null
    • NextDNs
    • 2 yrs ago
    • Reported - view

    Please provide a https://nextdns.io/diag

    • bschleifer
    • 2 yrs ago
    • Reported - view

    Here you go: https://nextdns.io/diag/f4a19620-54ce-11ed-8a23-89b7470467e9

      • NextDNs
      • 2 yrs ago
      • Reported - view

      bschleifer please try using the NextDNS IPs found in your setup tabs as system DNS in addition to DoH.

      • NextDNs
      • 2 yrs ago
      • Reported - view

      bschleifer also, before changing anything, could you please provide the the output of https://test.nextdns.io with nextdns disabled?

      • bschleifer
      • 2 yrs ago
      • Reported - view

      NextDNS Sure. But your first suggestion of modifying DNS makes no sense. That is already done. I'll do another test since I had to disable NextDNS just now.

      • bschleifer
      • 2 yrs ago
      • Reported - view

      NextDNS  

      {
"status": "unconfigured",
"resolver": "172.253.8.135",
"ecs": "67.23.144.0/24/0",
"srcIP": "67.23.144.140",
"server": "zepto-xrs-1"
}
      • NextDNs
      • 2 yrs ago
      • Reported - view

      bschleifer can you please rerun the diag without nextdns enabled as well? We are trying to understand what is going on here, there is definitely something abnormal.

      • bschleifer
      • 2 yrs ago
      • Reported - view

      NextDNS Sure thing. Here you go:

      https://nextdns.io/diag/68cf9660-5f0a-11ed-ac61-63f196dfbc58

      • NextDNs
      • 2 yrs ago
      • Reported - view

      bschleifer everything seems normal on the steering itself. You mentioned once a day, is it always happening at the same time every day?

      • bschleifer
      • 2 yrs ago
      • Reported - view

      NextDNS It is hit and miss. I had to stop using it. I'll try it again and if it fails I'll post something in here. 

      • NextDNs
      • 2 yrs ago
      • Reported - view

      bschleifer in yogadns, have you tried with the ultralow feature on?

      • bschleifer
      • 2 yrs ago
      • Reported - view

      NextDNS That is how it is currently configured. I tried both but right now it is set to "Use Ultra-Low Latency Network"

      • NextDNs
      • 2 yrs ago
      • Reported - view

      bschleifer with yoga and ultra low on, can you run another diag please?

      • bschleifer
      • 2 yrs ago
      • Reported - view

      NextDNS Here you go: https://nextdns.io/diag/894eeba0-5f70-11ed-9305-e52c90d6951d

      • bschleifer
      • 1 yr ago
      • Reported - view

      NextDNS It has been two weeks with no reply. This product has been so disappointing. I am left with having to cancel this service because support is only there when I complain. 

    • bschleifer
    • 2 yrs ago
    • Reported - view

    Is there expected to be any follow-up support for my issue? I have been reviewing this as an option for our organization and thus far this is not a solution that is corporate-ready.

      • Hey
      • 2 yrs ago
      • Reported - view

      bschleifer Pretty sure that Enterprise clients have an email address they can contact to, so if you're on the said plans, I'd go that route.

    • bschleifer
    • 2 yrs ago
    • Reported - view

    So once again NextDNS is timing out and I had to switch back over to Google. 

    • Reny_Neto
    • 2 yrs ago
    • Reported - view

    Following 

    • bschleifer
    • 1 yr ago
    • Reported - view

    To close the loop on this. Another two weeks went by with no reply. NextDNS has proven to be flaky, and I have been ghosted by support. I cancelled my subscription and look into other options for our organization. 

    • Jonas
    • 10 mths ago
    • Reported - view

    Same issue here. I'll give ControlD a try.

Login to reply

Content aside

  • 1 Likes
  • 10 mths agoLast active
  • 21Replies
  • 363Views
  • 5 Following