Service seems to be down today (time out 99% of the request)
Today about 8h ago, my "internet" seems to timeout.. ultimately I figured the isssue was with Next DNS.
It had been working flawless for the past 6 months, and this is a free service so I cant complain.
Not sure how to help you figuring out what is wrong..
it's definitively not on may end.
The DNS was set in windows network setting (and had been forking fine), I tried to see if switching to your app , or yoga dns would make a change but it did not..
Side not people using edge should know that edge by default bypass windows dns network setting to use its own DNS, if you want to use edge with Next DNS either set it manualy in edge or use next dns app or Yoga DNS
only log I could find
DnsCrypt log: Get "https://yoga.dns.nextdns.io/******?dns=yv4BAAABAAAAAAABAAACAAEAACkQAAAAAAAAFAAMABBF7ifZuw_mU3iZoOSAKQXr": net/http: request canceled (Client.Timeout exceeded while awaiting headers)
15 replies
-
It’s not necessarily at their end. It could be a borked router somewhere between your isp and their servers. They have a diag tool you can use and post the results. Or try a traceroute. I’m working from a tiny screen phone right now otherwise I’d give you a link to their diag tool. You should be able to find it by looking through their troubleshooting guides
-
Also there’s no difference in service between free and paid plans other than the 300K query limit
-
Please provide as https://nextdns.io/diag
-
report sent . here is a copy
Testing IPv6 connectivity
available: false
Fetching https://test.nextdns.io
Fetch error: Get "https://test.nextdns.io": unexpected EOF
Fetching PoP name for ultra low latency primary IPv4 (ipv4.dns1.nextdns.io)
Fetch error: Get "https://dns.nextdns.io/info": EOF
Fetching PoP name for ultra low latency secondary IPv4 (ipv4.dns2.nextdns.io)
Fetch error: Get "https://dns.nextdns.io/info": EOF
Fetching PoP name for anycast primary IPv4 (45.90.28.0)
Fetch error: Get "https://dns.nextdns.io/info": EOF
Fetching PoP name for anycast secondary IPv4 (45.90.30.0)
Fetch error: Get "https://dns.nextdns.io/info": EOF
Pinging PoPs
anexia-par: 6.999ms
virtua-par: 3.98ms
zepto-lon: 13.973ms
netbarista-par: 6.975ms
zepto-bru: 14.957ms
anexia-lon: 10.978ms
anexia-lux: 9.009ms
zepto-ams: 11.872ms
fusa-bru: 14.035ms
vultr-lon: 47.391ms
Traceroute for ultra low latency primary IPv4 (185.10.17.92)
2 192.168.1.1 1ms * 1ms
3 10.153.0.17 3ms 3ms 2ms
4 77.128.5.33 4ms 3ms 3ms
5 185.10.17.92 5ms 4ms 3ms
Traceroute for ultra low latency secondary IPv4 (193.168.204.73)
2 192.168.1.1 2ms 1ms 1ms
3 10.153.0.17 3ms 3ms 4ms
4 77.128.5.33 4ms 3ms 3ms
5 193.168.204.73 5ms 4ms 5ms
Traceroute for anycast primary IPv4 (45.90.28.0)
2 192.168.1.1 1ms 1ms 1ms
3 10.153.0.17 3ms 2ms 3ms
4 77.128.5.33 3ms 3ms 3ms
5 45.90.28.0 5ms 4ms 4ms
Traceroute for anycast secondary IPv4 (45.90.30.0)
2 192.168.1.1 1ms 1ms 1ms
3 10.153.0.17 3ms 2ms 2ms
4 77.128.5.33 4ms 3ms 3ms
5 45.90.30.0 4ms 3ms 3ms -
i'm using quad 9 as dns for the moment you need me to switch back to nextdns and redo the test?
-
I rerun the soft using next dns as dns (not sure if it send the report) (i switched back to quad to allow it once it was done).
Testing IPv6 connectivity
available: false
Fetching https://test.nextdns.io
Fetch error: Get "https://test.nextdns.io": dial tcp: lookup test.nextdns.io: no such host
Fetching PoP name for ultra low latency primary IPv4 (ipv4.dns1.nextdns.io)
Fetch error: Get "https://dns.nextdns.io/info": dial tcp: lookup ipv4.dns1.nextdns.io: no such host
Fetching PoP name for ultra low latency secondary IPv4 (ipv4.dns2.nextdns.io)
Fetch error: Get "https://dns.nextdns.io/info": dial tcp: lookup ipv4.dns2.nextdns.io: no such host
Fetching PoP name for anycast primary IPv4 (45.90.28.0)
Fetch error: Get "https://dns.nextdns.io/info": EOF
Fetching PoP name for anycast secondary IPv4 (45.90.30.0)
Fetch error: Get "https://dns.nextdns.io/info": EOF
Pinging PoPs
error: Get "https://router.nextdns.io/?limit=10&stack=dual": dial tcp: lookup router.nextdns.io: no such host
Traceroute error: lookup ipv4.dns1.nextdns.io: no such host
Traceroute error: lookup ipv4.dns2.nextdns.io: no such host
Traceroute for anycast primary IPv4 (45.90.28.0)
2 192.168.1.1 2ms 1ms 1ms
3 10.153.0.17 3ms 2ms 2ms
4 77.128.5.33 3ms 3ms 4ms
5 45.90.28.0 5ms 4ms 5ms
Traceroute for anycast secondary IPv4 (45.90.30.0)
2 192.168.1.1 1ms 1ms 1ms
3 10.153.0.17 2ms 2ms 3ms
4 77.128.5.33 4ms 3ms 4ms
5 45.90.30.0 4ms 4ms 4ms -
Apparently something on your network is blocking the resolution of domains under nextdns.io.
-
Please send the url generated by the diag tool and not its output.
-
ok futher investigation the issue seems local (my machine) as my phone connected on the same wifi network can work with next dns..
I looked at my host file (on the win machine) but could not find nextdns.io on the list .. any idea of other place to look ?
also : using and other NIC from the same computer that was not set up to use next dns => internet was working that's the initial reason why I believe the issue was not local.
having said that if i enable next dns with with other NIC , => not working ..
weird
-
I set up my router to use next dns.. to see what happen:
The machine with an issue could access the net.. but it did not use next dns and filtering was not working on that devise
Error while checking the current status.
Please talk to us if this problem persists after refreshing the page.
-
List of things that I've tried so far unsuccessfully:
-check for rules in win firewall
-disable windows firewall
-reset network interface (that reinstall the drivers according to windows)
-check the host file / remove all entry in host file
-setup the dns in the router
I can not figure whats wrong with that machine
-
More investigation on the machine that no longer work with next dns:
on any browser https://ping.nextdns.io/ does nothing:
When I inspect the page I see:Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://test-ipv6.nextdns.io/. (Reason: CORS request did not succeed). Status code: (null).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://a6draan917w.test.nextdns.io/. (Reason: CORS request did not succeed). Status code: (null).
Uncaught (in promise)
Object { stack: "$@https://ping.nextdns.io/static/js/main.96cb97b4.js:2:155055\nNe/</u.onerror@https://ping.nextdns.io/static/js/main.96cb97b4.js:2:166820\n", message: "Network Error", name: "AxiosError", code: "ERR_NETWORK", config: {…}, request: XMLHttpRequest }
asyncToGenerator.js:6:4
Error: Promised response from onMessage listener went out of scope
Content aside
- 4 mths agoLast active
- 15Replies
- 246Views
-
2
Following