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
-
Here is one more
-
I was just about to post about the same. The extend of the timeouts are not as large as the original post though. It happens a few times a day for like maximum 10 seconds. I then get the same error as the images above. Additionally, YogaDNS gives me the following error: " request canceled (Client.Timeout exceeded while awaiting headers)". It is really annoying.
-
Vincent van Duijnhoven How long has this been happening to you?
-
A. Glez. B. Longer than your week. I am aware of it for a few weeks now (I first used the nextDNS client that has no logging compared to YogaDNS but there it also happened I thought). Because it only happens for a few secs, I was fine with it but it keeps happening while when it happens, my internet works perfectly fine.
-
Vincent van Duijnhoven Have you had any luck with NextDNS support?
-
A. Glez. B. I didn't contact them yet also because I know the dev's also are watching these forums I prefer to discuss it here
-
Vincent van Duijnhoven Let us hope so.
-
-
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.
-
John DeCarlo Here
The servers in the list are DNS over HTTPS and will not work if dns.nextdns.io fails to resolve.
-
John DeCarlo https://i.imgur.com/JYTWGeq.png
I also downloaded the servers in YogaDNS. What next? the dns rule still points to my own, default dns profile
-
Vincent van Duijnhoven
To fix the time out go to Dns servers and select get dns servers from web. Select the two NextDNS servers. Relapse the ip address with the Ip address in this list.
-
Vincent van Duijnhoven
Ok got to Dns Servers and select the Nexdns server . Change 45.90.28.0 to 200.25.22.68 . Change dnscrypt-proxy to your ID xxxxxx. Save your work. Go to Nextdns-ipv6 change 2a07:a8c0:: to 2800:1e0:1060:2::4 Change dnscrypt-proxy to your ID xxxxxx. Save your work. . You can make a dns pool with these new nextdns servers. You can setup all the dns servers that I listed for you.
-
Vincent van Duijnhoven
After you setup your new ultralow nextdns servers change the dns rule to your new nextdns pool dns servers. Test it out and let me know how it works. My Nextdns is flying. Very fast no time outs.
-
A. Glez. B.
Your Ultralow Dns servers are:
ipv6-edgeuno-scl-1.edge.nextdns.io
2800:1e0:1060:2::4ipv4--edgeuno-scl-1.edge.nextdns.io
200.25.22.68ipv6-edgeuno-bue-1.edge.nextdns.io
2800:1e0:1030:2::4ipv4-edgeuno-bue-1.edge.nextdns.io
200.25.62.68 -
Vincent van Duijnhoven
These are the new Ultralow NextDNS servers
ipv4-vultr-ams-1.edge.nextdns.io
95.179.134.211ipv6-vultr-ams-1.edge.nextdns.io
2001:19f0:5001:1faf:5400:2ff:fec8:7d49ipv4-zepto-ams-1.edge.nextdns.io
78.142.193.36ipv4-anexia-fra-1.edge.nextdns.io
217.146.22.163ipv6-anexia-fra-1.edge.nextdns.io
2a00:11c0:e:ffff:1::dipv4-zepto-fra-1.edge.nextdns.io
89.187.169.24ipv6-zepto-fra-1.edge.nextdns.io
2a0b:4341:704:24:5054:ff:fe91:8a6cipv4-vultr-fra-1.edge.nextdns.io
199.247.16.158ipv6-vultr-fra-1.edge.nextdns.io
2a05:f480:1800:8ed:5400:2ff:fec8:7e46ipv4-fusa-bru-1.edge.nextdns.io
185.18.148.91ipv6-fusa-bru-1.edge.nextdns.io
2a04:b80:1:30::2ipv4-zepto-lon-1.edge.nextdns.io
178.239.160.221ipv6-zepto-lon-1.edge.nextdns.io
2a0f:3b03:100:2:5054:ff:fe90:4a77ipv4-anexia-lon-1.edge.nextdns.io
2a00:11c0:8:4::9ipv6-anexia-lon-1.edge.nextdns.io
2a00:11c0:8:4::9
Sorry. Please use these ip addresses ..
-
John DeCarlo 2 questions:
1) should I also change the URL to the one above your ultra low DNS ip's? servers? https://i.imgur.com/8UusVUo.png
2) Why do we have to manually setup the ultra low DNS servers? why aren't they enabled by default?
-
Vincent van Duijnhoven
That is correct. You have setup your new Ultralow NextDNS servers ..
-
John DeCarlo Hey. The amount of time requests seems to have decreased significantly.
I have one remaining question. Where did you find the addresses and IP's of the low latency server? I can't find that anywhere on the official nextdns sites.
-
Vincent van Duijnhoven
When you go to https://ping.nextdns.io
vultr-ewr
Ipv6-vultr-ewr-1.edge.nextdns.io
ipv4-vultr-ewr-1.edge.nextdns.io
All you have to do is put
How is you nextdns working?
-
John DeCarlo this is a very bad idea as this can break any time with no notice.
-
Olivier Poitrey
Okay. dns.nextdns.io has a resolution problem. I fixed the resolution in YogaDNS . Can you look at YogaDNS configuration. It is very broken
-
John DeCarlo what resolution problem does it have? Do you have a dig output example?
-
Olivier Poitrey
YogaDNS default Nextdns configuration has resolution and time out problems. I am trying to pinpoint where the timeouts resolution resolver is happening.
-
John DeCarlo Olivier Poitrey So it is not adviced to manually add the ultra-low latency server like this? In the first setup of yogaDNS, I entered nextDNS and I checked "use ultra-low latency network". Though adding those ultra-low latency servers reduces the number of request timeouts notable, I wondered why because that simple check should take care of that.
-
Is it now advised to set up the low latency servers myself if it can break at any time? What other solution is there to use the best low latency servers without setting them up myself. The checkbox "use ultra-low latency network" in yogaDNS is not doing its job properly at least
-
Content aside
- 3 yrs agoLast active
- 51Replies
- 1017Views
-
5
Following