NextDNS down in Moscow
Hi, today I have found that NextDNS doesn’t work.
Sites and apps don’t work if I try to use NextDNS as DNS provider in Moscow Russia. How to solve this issue.
7 replies
-
Same
-
Same
-
Hello.
Yes, I can confirm that my internet access stopped working today as well when using my NextDNS profile. No websites are accessible.
However, everything starts working again as soon as I enable my VPN.
Below are the results of the tests I ran in PowerShell without a VPN:
Test 1
curl.exe --doh-url "https://dns.nextdns.io/YOUR_PROFILE_ID" https://example.com -I curl: (6) Could not resolve hostnameTest 2
curl.exe -v --doh-url "https://dns.nextdns.io/YOUR_PROFILE_ID" -I https://example.com * DoH: Too small type A for example.com * DoH: Too small type AAAA for example.com * shutting down connection #0 curl: (6) Could not resolve hostnameTest 3
curl.exe -v -I --connect-timeout 10 "https://dns.nextdns.io/YOUR_PROFILE_ID" * Host dns.nextdns.io:443 was resolved. * IPv6: 2a0e:5c41:2:7c:5054:ff:fe44:c7db, 2a0d:5642:201:108:5054:ff:fe3c:907 * IPv4: 45.142.246.128, 45.150.243.134 * Trying [2a0e:5c41:2:7c:5054:ff:fe44:c7db]:443... * schannel: disabled automatic use of client certificate * ALPN: curl offers http/1.1 * Connection timed out after 10001 milliseconds * closing connection #0 curl: (28) Connection timed out after 10001 millisecondsTest 4
curl.exe -4 -v -I --connect-timeout 10 "https://dns.nextdns.io/YOUR_PROFILE_ID" * Host dns.nextdns.io:443 was resolved. * IPv6: (none) * IPv4: 45.142.246.128, 45.150.243.134 * Trying 45.142.246.128:443... * schannel: disabled automatic use of client certificate * Connection timed out after 10003 milliseconds * closing connection #0 curl: (28) Connection timed out after 10003 millisecondsTest 5
curl.exe -4 -v -I --connect-timeout 10 --resolve dns.nextdns.io:443:45.150.243.134 "https://dns.nextdns.io/YOUR_PROFILE_ID" * Added dns.nextdns.io:443:45.150.243.134 to DNS cache * Hostname dns.nextdns.io was found in DNS cache * Trying 45.150.243.134:443... * Connection timed out after 10002 milliseconds * closing connection #0 curl: (28) Connection timed out after 10002 millisecondsTest 6
curl.exe -4 -v -I --connect-timeout 10 "https://anycast.dns1.nextdns.io/YOUR_PROFILE_ID/dns-query" * Host anycast.dns1.nextdns.io:443 was resolved. * IPv6: (none) * IPv4: 45.90.28.0 * Trying 45.90.28.0:443... * Connection timed out after 10001 milliseconds * closing connection #0 curl: (28) Connection timed out after 10001 millisecondsTest 7
curl.exe -4 -v -I --connect-timeout 10 --resolve dns.nextdns.io:443:45.90.30.0 "https://dns.nextdns.io/YOUR_PROFILE_ID" * Added dns.nextdns.io:443:45.90.30.0 to DNS cache * Hostname dns.nextdns.io was found in DNS cache * Trying 45.90.30.0:443... * Connection timed out after 10002 milliseconds * closing connection #0 curl: (28) Connection timed out after 10002 millisecondsLocation and ISP: Omsk, Russia. Internet service provider: dom.ru.
Could you please investigate this issue and clarify why NextDNS is no longer accessible without a VPN? Thank you.
-
Could you please provide a https://nextdns.io/diag
-
У меня тоже не работает. Работает только с VPN. Без него статус сети показывает «подключено», но трафик не проходит в интернет.
Content aside
-
7
Votes
- 9 hrs agoLast active
- 7Replies
- 123Views
-
11
Following
