0

Timeout issues since last week

For the original post in Reddit click here

Since last week I've been having issues and the log from YogaDNS is full of request timeouts including but not limited to dns.nextdns.io and steering.nextdns.io . If I set YogaDNS to bypass everything works fine. I waited this long before asking about it because this issues are mostly temporary but this time it has been a week and I'm still having problems.

I pay for NextDNS because I like it but that is conditional to the service working as expected. As of now it is having a very negative impact on my job because my work VPN connections keep dropping.

 

51 replies

null
    • John_DeCarlo
    • 3 yrs ago
    • Reported - view

    I have YogaDNS  working on Windows 10 with no time outs.

    Can you post your https://test.nextdns.io https://router.nextdns.io and https://dns.nextdns.io/info

    In YogaDNS  go to Get dns Servers from web and find the two Nextdns servers and import them.

      • olivier
      • 3 yrs ago
      • Reported - view

      Vincent van Duijnhoven please provide a https://nextdns.io/diag

      • Vincent_van_Duijnhoven
      • 3 yrs ago
      • Reported - view

      Olivier Poitrey The exe file is broken. It can't execute on my pc (win 10 64bit). Adding an exception in the anti-virus does not solve it.

    • John_DeCarlo
    • 3 yrs ago
    • Reported - view

    Also post https://ping.nextdns.io. Thanks

    • John_DeCarlo
    • 3 yrs ago
    • Reported - view

    ipv6-edgeuno-scl-1.edge.nextdns.io
    2800:1e0:1060:2::4   

    ipv4--edgeuno-scl-1.edge.nextdns.io
    200.25.22.68  

    ipv6-edgeuno-bue-1.edge.nextdns.io
    2800:1e0:1030:2::4  

    ipv4-edgeuno-bue-1.edge.nextdns.io
    200.25.62.68

    ipv4-heficed-sao-1.edge.nextdns.io
    191.96.71.28

    ipv6-heficed-sao-1.edge.nextdns.io
    2803:80:8001:94::

    ipv4-anexia-sao-1.edge.nextdns.io
    37.252.238.25

    ipv6--anexia-sao-1.edge.nextdns.io
    2a00:11c0:f:ffff::5

      • AGlezb
      • 3 yrs ago
      • Reported - view

      John DeCarlo Just added SCL and BUE to the top of the pool. Thanks.

      • John_DeCarlo
      • 3 yrs ago
      • Reported - view

      A. Glez. B. 

      Thank you. Let me know how it works. It should fix your time outs.

      • AGlezb
      • 3 yrs ago
      • Reported - view

      John DeCarlo

      Something weird is happening.  When using check in YogaDNS I'm getting:

      • 140+ ms most of the time.
      • Sub 20 ms some times but not very often
      • Very rarely a 100+ ms difference between close and default servers

      Disabling the firewall and rebooting the router didn't help. Your adviced helped a bit but I'm stil getting a ton of timeouts.

      • John_DeCarlo
      • 3 yrs ago
      • Reported - view

      A. Glez. B. 

      How is you Ipv6 network. Can you tracert 2800:1e0:1060:2::4 and tracert 2800:1e0:1030:2::4 . can you also tracert anycat.dns.nextdns.io and dns.nextdns.io .

      • AGlezb
      • 3 yrs ago
      • Reported - view

      John DeCarlo My ISP doesn't support IPv6 yet.

      • John_DeCarlo
      • 3 yrs ago
      • Reported - view

      A. Glez. B. A. Glez. B. 

       

      Okay remove all the ipv6 dns servers. Use only ipv4 servers.  Test it out. How is Cloudflare. tracert 1.1.1.1

      • AGlezb
      • 3 yrs ago
      • Reported - view

      John DeCarlo Trace plus a couple of Diag reports coming up. 😣

      https://nextdns.io/diag/76310370-76f9-11eb-966c-cd4910ff3d46

      https://nextdns.io/diag/aca20f80-76cc-11eb-966c-cd4910ff3d46

      • John_DeCarlo
      • 3 yrs ago
      • Reported - view

      A. Glez. B. 

      Add a new dns server

      https://ultalow.dns1.nextdns.io/xxxxxx you ID

      200.25.22.68 

      New Dns server 

      https://anycast.dns1.nextdns.io/xxxxxx you ID

      45.90.28.xxx your ip address

      Setup a new dns pool with these two dns servers

      Add dns server  1.1.1.1

      https://1dot1dot1dot1.cloudflare-dns.com/dns-query

      Setup a new dns rule and add these domain names

      *.steering.nextdns.io;*.dns.nextdns.io;*.dns1.nextdns.io;*.dns2.nextdns.io   

      • John_DeCarlo
      • 3 yrs ago
      • Reported - view

      John DeCarlo 

       

      https://ultralow.dns1.nextdns.io/xxxxxx your id

      • inkflaw
      • 3 yrs ago
      • Reported - view

      John DeCarlo It is useful, thans a lot, but why I can not use dns.nextdns.io? It's because of my IPS?

    • AGlezb
    • 3 yrs ago
    • Reported - view

    My apologies to NextDNS because this issue was not their fault.

    I have 2 NICs, Intel 1 Ggps and Realtek 2.5 Gbps, and had the cable connected to the Realtek which is failing a lot for whatever reason. DNS issues went away the moment I switched to the Intel NIC. I intend to fix the issue with the Realtek but that can wait.

    John DeCarlo Thank you for your help.

      • John_DeCarlo
      • 3 yrs ago
      • Reported - view

      TA. Glez. B.  Thanks for the update.  Hopefully your DNS lookups will fly. 

      • AGlezb
      • 3 yrs ago
      • Reported - view

      John DeCarlo Thanks 😄

    • inkflaw
    • 3 yrs ago
    • Reported - view

    I had the same wrong, but I got the error since last week, and I can not use NextDNS service whatever DoT or DoH at anytime.

    • inkflaw
    • 3 yrs ago
    • Reported - view

    Unfortunately, I can not use the anycast or the ultalow URL to connect NextDNS today.

    I do not know how to trace route, but I had test my network by the NextDNS diag at a few hours ago, hope it's useful.

    https://nextdns.io/diag/fe891e00-815e-11eb-abe8-11b40072f372

    https://nextdns.io/diag/f933d4b0-815c-11eb-abe8-11b40072f372

    • AGlezb
    • 3 yrs ago
    • Reported - view

    Gigabyte posted a new LAN driver [10.47.121.2021 (IM disabled) ] which fixes my issue. Release notes literally read: Fix random LAN disconnected phenomenon 😄

      • John_DeCarlo
      • 3 yrs ago
      • Reported - view

      A. Glez. B.  That's awesome. 

Login to reply

Content aside

  • 3 yrs agoLast active
  • 51Replies
  • 1017Views
  • 5 Following