0

Problem with DoH3

Hello. I have a problem with DoH3. All other third-party DNS services that use the DoH3 protocol work well and reliably. But nextDNS's DNS service doesn't. Every two or three requests, the connection is constantly lost when opening websites, and only after a reboot does the request to the desired website resume. I can't even figure out what the problem is. I've noticed that using other third-party DoH3 DNS services doesn't have this problem.  

 

5 replies

null
    • NextDNS_Network
    • 5 days ago
    • Reported - view

    Please provide a https://nextdns.io/diag

      • Home_user1
      • 5 days ago
      • Reported - view

       

      Welcome to NextDNS network diagnostic tool.

      This tool will capture latency and routing information regarding
      the connectivity of your network with NextDNS.

      The source code of this tool is available at https://github.com/nextdns/diag

      Do you want to continue? (press enter to accept)

      Testing IPv6 connectivity
        available: false
      Fetching https://test.nextdns.io
        status: ok
        client: 37.114.129.13
        protocol: DOH3
        dest IP: 45.142.246.128
        server: zepto-mow-1
      Fetching PoP name for ultra low latency primary IPv4 (ipv4.dns1.nextdns.io)
      Fetch error: Get "https://dns.nextdns.io/info": read tcp 192.168.100.34:7031->37.252.245.241: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.
      Fetching PoP name for ultra low latency secondary IPv4 (ipv4.dns2.nextdns.io)
      Fetch error: Get "https://dns.nextdns.io/info": read tcp 192.168.100.34:9540->95.174.68.136: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.
      Fetching PoP name for anycast primary IPv4 (45.90.28.0)
      Fetch error: Get "https://dns.nextdns.io/info": read tcp 192.168.100.34:9750->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.
      Fetching PoP name for anycast secondary IPv4 (45.90.30.0)
      Fetch error: Get "https://dns.nextdns.io/info": read tcp 192.168.100.34:9751->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.
      Pinging PoPs
        worldstream-tbs: 72.736ms
        edgeuno-ist: 75.996ms
        edis-kiv: 84.81ms
        hetzner-tbs: 84.462ms
        netshop-nic: 92.307ms
        zepto-ist: 99.831ms
        anexia-iev: 100.195ms
        lightnode-ruh: 154.69ms
        anexia-dxb: 186.62ms
        melbicom-dxb: 189.552ms
      Traceroute for ultra low latency primary IPv4 (37.252.245.241)
          1  192.168.100.1    1ms   1ms   1ms
          2 10.221.235.254    3ms   3ms   2ms
          3     10.8.29.98    4ms   4ms   3ms
          4    10.8.32.129    4ms   4ms   4ms
          5    10.8.32.115    4ms   4ms   4ms
          6      10.8.52.7    6ms   6ms   5ms
          7 109.235.192.141    6ms   5ms   5ms
          8    10.240.3.34    6ms   6ms   5ms
          9  184.105.80.37   80ms  80ms  81ms
         10                   *     *     *
         11                   *     *     *
         12  216.66.85.170   85ms  84ms  84ms
         13  213.202.5.248  201ms   *     *
         14  213.202.6.201  214ms 211ms 223ms
         15  213.202.6.193  212ms   *     *
         16    134.0.221.3  200ms 199ms 199ms
         17    213.202.2.1  200ms 200ms 199ms
         18 37.252.245.241  210ms 210ms 210ms
      Traceroute for ultra low latency secondary IPv4 (95.174.68.136)
          1  192.168.100.1    1ms   1ms   1ms
          2 10.221.235.254    4ms   3ms   2ms
          3     10.8.29.98    4ms   4ms   4ms
          4    10.8.32.129    5ms   3ms   4ms
          5    10.8.32.115    5ms   5ms   4ms
          6      10.8.52.7    6ms   6ms   5ms
          7 109.235.192.141    5ms   5ms   5ms
          8  10.240.164.38    6ms   5ms   5ms
          9   185.1.226.96   68ms  67ms  67ms
         10  5.154.154.126  191ms 190ms 191ms
         11 102.217.165.134  182ms 181ms 182ms
         12  95.174.68.136  188ms 187ms 187ms
      Traceroute for anycast primary IPv4 (45.90.28.0)
          1  192.168.100.1    1ms   1ms   1ms
          2 10.221.235.254    4ms   4ms   4ms
          3     10.8.29.98    4ms   4ms   3ms
          4    10.8.32.129    4ms   3ms   3ms
          5    10.8.32.115    4ms   5ms   5ms
          6      10.8.52.7    6ms   5ms   5ms
          7 109.235.192.141    6ms   6ms   6ms
          8  10.240.164.38    6ms   5ms   4ms
          9                   *     *     *
         10                   *     *     *
         11                   *     *     *
         12                   *     *     *
         13 192.248.130.47   69ms  68ms  69ms
         14     45.90.28.0   78ms  78ms  77ms
      Traceroute for anycast secondary IPv4 (45.90.30.0)
          1  192.168.100.1    1ms   1ms   1ms
          2 10.221.235.254    4ms   4ms   4ms
          3     10.8.29.98    4ms   4ms   4ms
          4    10.8.32.129    4ms   4ms   4ms
          5    10.8.32.115    5ms   4ms   4ms
          6      10.8.52.7    6ms   6ms   5ms
          7 109.235.192.141    6ms   5ms   6ms
          8  10.240.164.38    6ms   5ms   6ms
          9  185.1.226.169   39ms  39ms  38ms
         10     45.90.30.0   38ms  38ms  38ms
      Do you want to send this report? [Y/n]:

      • Home_user1
      • 5 days ago
      • Reported - view
      • Home_user1
      • 4 days ago
      • Reported - view

       

      Done

      • Home_user1
      • 2 days ago
      • Reported - view

       

       

      did you receive the data I sent?  

Content aside

  • 2 days agoLast active
  • 5Replies
  • 123Views
  • 2 Following