0

Problems

Hello everybody,

we use NextDNS in our office. Unfortunately, it happens several times a day that a connection to a website cannot be established.
I have already run the diagnostic tool. However, it supports because apparently no connection is possible. If I remove NextDNS in the Fritzbox, it works again. At some point it will work again on its own.
Does anyone know the problem or a solution?

9 replies

null
    • Robin_
    • 3 yrs ago
    • Reported - view
    • Pro subscriber ✓
    • DynamicNotSlow
    • 3 yrs ago
    • Reported - view

    i had same problems in past and my solution is using Quad9 in Fritzbox while NextDNS on device like in e.g. Edge browser

    • Robin_
    • 3 yrs 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
      Fetch error: Get "https://test.nextdns.io": dial tcp: lookup test.nextdns.io: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
    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: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
    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: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
    Fetching PoP name for anycast primary IPv4 (45.90.28.0)
      zepto-fra: 20.516ms
    Fetching PoP name for anycast secondary IPv4 (45.90.30.0)
      anexia-ams: 21.803ms
    Pinging PoPs
      error: Get "https://router.nextdns.io/?limit=10&stack=dual": dial tcp: lookup router.nextdns.io: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
      Traceroute error: lookup ipv4.dns1.nextdns.io: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
      Traceroute error: lookup ipv4.dns2.nextdns.io: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
    Traceroute for anycast primary IPv4 (45.90.28.0)
        2 195.14.226.161   15ms  15ms  15ms
        3  195.14.215.57   16ms  16ms  15ms
        4    87.79.17.25   16ms  15ms  15ms
        5  195.14.195.54   15ms  15ms  15ms
        6  91.213.211.28   19ms  18ms  19ms
        7  45.11.107.129   19ms  18ms  18ms
        8     45.90.28.0   19ms  18ms  18ms
    Traceroute for anycast secondary IPv4 (45.90.30.0)
        1    192.168.2.1    1ms   1ms   1ms
        2 195.14.226.161   15ms  14ms  14ms
        3  195.14.215.61   15ms  14ms  14ms
        4 81.173.192.118   15ms  15ms  14ms
        5  80.81.195.166   18ms  17ms  19ms
        6 144.208.208.143   18ms  17ms  18ms
        7     45.90.30.0   18ms  17ms  17ms

    • NextDNs
    • 3 yrs ago
    • Reported - view

    Is there any form of error logs on the Fritzbox regarding DNS?

      • Robin_
      • 3 yrs ago
      • Reported - view

      NextDNS where can i see this log?

      • Pro subscriber ✓
      • DynamicNotSlow
      • 3 yrs ago
      • Reported - view

      Robin left side, open menu at bottom

      • Robin_
      • 3 yrs ago
      • Reported - view

      NextDNS There are no logs for DNS Problems.

      • Pro subscriber ✓
      • DynamicNotSlow
      • 3 yrs ago
      • Reported - view

      Robin no but for error's generally

    • Robin_
    • 3 yrs ago
    • Reported - view

    No errors. I don’t know what’s the problem

Content aside

  • 3 yrs agoLast active
  • 9Replies
  • 271Views
  • 2 Following