10

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. 

13 replies

null
    • Tom.43
    • 10 days ago
    • Reported - view

    Same

    • pashajalest
    • 10 days ago
    • Reported - view

    Same

    • OmichNextDNS
    • 10 days ago
    • Reported - view

    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 hostname

    Test 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 hostname

    Test 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 milliseconds

    Test 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 milliseconds

    Test 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 milliseconds

    Test 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 milliseconds

    Test 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 milliseconds

    Location 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.

    • NextDNs
    • 10 days ago
    • Reported - view

    Could you please provide a https://nextdns.io/diag

      • OmichNextDNS
      • 10 days ago
      • Reported - view

       

      I tried to download your diagnostic tool (diag.exe) using the link provided, but I get the following error message:

      "Error 1101 Ray ID: a519ccbc2a28a167 • 2026-10-28 12:03:52 UTC
      Worker threw exception"

      How can I download it?

      • Ruslan.3
      • 10 days ago
      • Reported - view

       

      Вот перевод ваших фраз:

      Это скриншот диагностического теста с выключенным VPN и включенным профилем NextDNS.

      diag_nextdns
      • OmichNextDNS
      • 9 days ago
      • Reported - view

       

      I managed to download your diagnostic tool. I ran it without a VPN. Below are the results, formatted for readability.

      NextDNS Network Diagnostic Report

      1. Initial Connectivity Tests

      IPv6 connectivity: Available (true)

      Test URL: https://test.nextdns.io

      Result:

      Fetch error: Get "https://test.nextdns.io":
net/http: TLS handshake timeout

      2. Fetching NextDNS PoP Information

      All attempts to retrieve Point of Presence (PoP) information failed.

      Ultra-low latency — Primary IPv4

      Hostname: ipv4.dns1.nextdns.io
      Destination IP: 45.142.246.128

      Fetch error: Get "https://dns.nextdns.io/info":
read tcp 192.168.1.27:60949->45.142.246.128:443: wsarecv:
A connection attempt failed because the connected party did not
properly respond after a period of time, or established connection
failed because connected host has failed to respond.

      Ultra-low latency — Secondary IPv4

      Hostname: ipv4.dns2.nextdns.io
      Destination IP: 45.150.243.134

      Fetch error: Get "https://dns.nextdns.io/info":
dial tcp 45.150.243.134:443: connectex:
A connection attempt failed because the connected party did not
properly respond after a period of time, or established connection
failed because connected host has failed to respond.

      Anycast — Primary IPv4

      Destination IP: 45.90.28.0

      Fetch error: Get "https://dns.nextdns.io/info":
read tcp 192.168.1.27:60951->45.90.28.0:443: wsarecv:
A connection attempt failed because the connected party did not
properly respond after a period of time, or established connection
failed because connected host has failed to respond.

      Anycast — Secondary IPv4

      Destination IP: 45.90.30.0

      Fetch error: Get "https://dns.nextdns.io/info":
read tcp 192.168.1.27:60952->45.90.30.0:443: wsarecv:
A connection attempt failed because the connected party did not
properly respond after a period of time, or established connection
failed because connected host has failed to respond.

      Ultra-low latency — Primary IPv6

      Destination IP: 2a0e:5c41:2:7c:5054:ff:fe44:c7db

      Fetch error: Get "https://dns.nextdns.io/info":
read tcp [2a03:1ac0:6dc2:7207:8019:8de8:6e87:f71c]:60953->
[2a0e:5c41:2:7c:5054:ff:fe44:c7db]:443: wsarecv:
A connection attempt failed because the connected party did not
properly respond after a period of time, or established connection
failed because connected host has failed to respond.

      Ultra-low latency — Secondary IPv6

      Destination IP: 2a0d:5642:201:108:5054:ff:fe3c:907

      Fetch error: Get "https://dns.nextdns.io/info":
read tcp [2a03:1ac0:6dc2:7207:8019:8de8:6e87:f71c]:60955->
[2a0d:5642:201:108:5054:ff:fe3c:907]:443: wsarecv:
A connection attempt failed because the connected party did not
properly respond after a period of time, or established connection
failed because connected host has failed to respond.

      Anycast — Primary IPv6

      Destination IP: 2a07:a8c0::

      Fetch error: Get "https://dns.nextdns.io/info":
read tcp [2a03:1ac0:6dc2:7207:8019:8de8:6e87:f71c]:60957->
[2a07:a8c0::]:443: wsarecv:
A connection attempt failed because the connected party did not
properly respond after a period of time, or established connection
failed because connected host has failed to respond.

      Anycast — Secondary IPv6

      Destination IP: 2a07:a8c1::

      Fetch error: Get "https://dns.nextdns.io/info":
read tcp [2a03:1ac0:6dc2:7207:8019:8de8:6e87:f71c]:60958->
[2a07:a8c1::]:443: wsarecv:
A connection attempt failed because the connected party did not
properly respond after a period of time, or established connection
failed because connected host has failed to respond.

      3. PoP Ping Test

      Pinging PoPs

Error:
Get "https://dns.nextdns.io/servers":
net/http: TLS handshake timeout

      4. IPv4 Traceroute Results

      Ultra-low latency — Primary IPv4

      Destination: 45.142.246.128

      HopIP addressRTT 1RTT 2RTT 3

      1 192.168.1.1 1 ms 1 ms 1 ms
      2 172.21.191.252 0 ms 0 ms 0 ms
      3 109.194.120.18 1 ms 1 ms 2 ms
      4 188.234.131.100 46 ms 42 ms 42 ms
      5 188.234.131.101 45 ms 42 ms 42 ms
      6 10.32.0.25 51 ms 42 ms 42 ms
      7 No response (*) * * *
      8 No response (*) * * *
      9 45.142.246.128 43 ms 42 ms 43 ms

      Ultra-low latency — Secondary IPv4

      Destination: 45.150.243.134

      HopIP addressRTT 1RTT 2RTT 3

      1 192.168.1.1 1 ms 1 ms 0 ms
      2 172.21.191.252 1 ms 1 ms 0 ms
      3 109.194.120.18 0 ms 2 ms 2 ms
      4 213.248.97.53 46 ms 44 ms 45 ms
      5 213.248.97.52 45 ms 45 ms 45 ms
      6 62.115.139.51 95 ms 95 ms 95 ms
      7 62.115.122.35 66 ms 66 ms 66 ms
      8 62.115.122.147 74 ms 74 ms 82 ms
      9 62.115.143.65 67 ms 67 ms 67 ms
      10 62.115.143.66 77 ms 76 ms 75 ms
      11 62.115.139.54 79 ms 79 ms 80 ms
      12 62.115.123.129 93 ms 93 ms 93 ms
      13 62.115.210.9 92 ms 92 ms 92 ms
      14 156.146.32.47 93 ms 93 ms 93 ms
      15 45.150.243.134 92 ms 92 ms 92 ms

      Anycast — Primary IPv4

      Destination: 45.90.28.0

      HopIP addressRTT 1RTT 2RTT 3

      1 192.168.1.1 1 ms 1 ms 0 ms
      2 172.21.191.252 0 ms 0 ms 0 ms
      3 109.194.120.18 0 ms 2 ms 1 ms
      4 188.234.131.100 93 ms 51 ms 44 ms
      5 188.234.131.101 42 ms 43 ms 43 ms
      6 10.32.0.25 43 ms 42 ms 41 ms
      7 No response (*) * * *
      8 No response (*) * * *
      9 45.90.28.0 42 ms 43 ms *

      Anycast — Secondary IPv4

      Destination: 45.90.30.0

      HopIP addressRTT 1RTT 2RTT 3

      1 192.168.1.1 1 ms 1 ms 1 ms
      2 172.21.191.252 0 ms 0 ms 1 ms
      3 109.194.120.18 2 ms 2 ms 2 ms
      4 213.248.97.53 44 ms 45 ms 45 ms
      5 No response (*) * * *
      6 62.115.139.51 79 ms 80 ms 80 ms
      7 62.115.118.109 55 ms 55 ms 55 ms
      8 80.239.169.98 55 ms 56 ms 55 ms
      9 45.90.30.0 56 ms 55 ms 56 ms

      5. IPv6 Traceroute Results

      Ultra-low latency — Primary IPv6

      Destination: 2a0e:5c41:2:7c:5054:ff:fe44:c7db

      HopIP addressRTT 1RTT 2RTT 3

      1 1ac0:6dc2:7207::1:0 1 ms 1 ms 1 ms
      2 2698:5400::503:0 1 ms 1 ms 0 ms
      3 2698:5400::1e02:0 2 ms 2 ms 2 ms
      4 2698:a100:da:2:5:7629:31:0 49 ms 42 ms 42 ms
      5 2698:a100:da:2:5:7629:36:0 42 ms 43 ms 42 ms
      6 f900:0:200::2:0 42 ms 48 ms 45 ms
      7 No response (*) * * *
      8 5c41:ff00::9:37:0 42 ms 42 ms 42 ms
      9 5c41:2:7c:5054:ff:fe44:c7db:0 43 ms 43 ms 45 ms

      Ultra-low latency — Secondary IPv6

      Destination: 2a0d:5642:201:108:5054:ff:fe3c:907

      HopIP addressRTT 1RTT 2RTT 3

      1 1ac0:6dc2:7207::1:0 1 ms 1 ms 1 ms
      2 2698:5400::503:0 2 ms 0 ms 0 ms
      3 2698:5400::1e02:0 4 ms 1 ms 0 ms
      4 2035:0:114d::2:0 39 ms 36 ms 36 ms
      5 2035:0:114d::1:0 45 ms 44 ms 45 ms
      6 2034:a:3a3:: * 51 ms *
      7 2034:a:30d::1:0 51 ms 51 ms 51 ms
      8 2034:a:3cf::1:0 53 ms 54 ms 53 ms
      9 2034:a:3d0:: 59 ms 59 ms 59 ms
      10 2034:a:3ce:: 74 ms 74 ms 75 ms
      11 2034:a:2a5::1:0 81 ms 81 ms 82 ms
      12 2035:0:2eaa::2:0 87 ms 87 ms 87 ms
      13 6ea0:8:1350:5053::2:0 87 ms 87 ms 87 ms
      14 5642:201:108:5054:ff:fe3c:907:0 87 ms 87 ms 87 ms

      Anycast — Primary IPv6

      Destination: 2a07:a8c0::

      HopIP addressRTT 1RTT 2RTT 3

      1 1ac0:6dc2:7207::1:0 1 ms 1 ms 1 ms
      2 2698:5400::503:0 0 ms 0 ms 0 ms
      3 2698:5400::1e02:0 2 ms 2 ms 0 ms
      4 2698:a100:da:2:5:7629:31:0 42 ms 42 ms 41 ms
      5 2698:a100:da:2:5:7629:36:0 42 ms 43 ms 42 ms
      6 f900:0:200::2:0 44 ms 45 ms 42 ms
      7 No response (*) * * *
      8 5c41:ff00::9:37:0 42 ms 42 ms 42 ms
      9 a8c0:: 43 ms * 43 ms

      Anycast — Secondary IPv6

      Destination: 2a07:a8c1::

      HopIP addressRTT 1RTT 2RTT 3

      1 1ac0:6dc2:7207::1:0 1 ms 0 ms 0 ms
      2 2698:5400::503:0 0 ms 0 ms 0 ms
      3 2698:5400::1e02:0 2 ms 2 ms 2 ms
      4 2035:0:114d::2:0 36 ms 36 ms 36 ms
      5 2035:0:114d::1:0 44 ms 44 ms 44 ms
      6 2034:a:39a:: 54 ms 54 ms 54 ms
      7 2035:0:2cf::2:0 49 ms 49 ms 50 ms
      8 a8c1:: 54 ms 54 ms 54 ms

      The diagnostic tool then prompted:

      Do you want to send this report? [Y/n]:
      • Gayratshok_Berdiev
      • 6 hrs ago
      • Reported - view

       As I understand it, the server for Russia has changed. Are there any plans to offer a solution for Russians so they can use NextDNS as before? For example, a NextDNS package that could be installed on their own server to forward requests to NextDNS. Yes, it’s possible to set this up yourself, but it’s difficult for many people.

    • DeadSocket
    • 10 days ago
    • Reported - view

    Confirmed. NextDNS is also down in St. Petersburg. My internet and the internet connections of several people I know who use NextDNS stopped working today. Roskomnadzor has probably blocked the nextdns.io domain. It no longer loads without a VPN or proxy. As a result, DoH/DoT configurations have stopped working. Well, we're screwed...

    • Ruslan.3
    • 10 days ago
    • Reported - view

    У меня тоже не работает. Работает только с VPN. Без него статус сети показывает «подключено», но трафик не проходит в интернет.

    • Gayratshok_Berdiev
    • 10 days ago
    • Reported - view

    Hello. I am a user from Russia. NextDNS has been blocked by the state DPI (TSPU, Technical Means for Countering Threats). This can be verified using the "dpi-detector" utility or by observing the unavailability in any DNS speed test application. 

    I don't know how to hide images behind a spoiler, apologies if they take up too much space.

    https://github.com/Runnin4ik/dpi-detector
    https://play.google.com/store/apps/details?id=com.catinthebox.dnsspeedtest

    Is there possibly a less public endpoint that hasn't been blocked yet?

     

    • Ivan.23
    • 10 days ago
    • Reported - view

    Komi Republic, Syktyvkar. NextDNS works on a wired internet connection. It does not work on mobile internet. Mobile operator Yota

    • alitair55
    • 8 days ago
    • Reported - view

    Same problem

Login to reply

Content aside

  • 10 Votes
  • 6 hrs agoLast active
  • 13Replies
  • 426Views
  • 13 Following