1

Issue accessing NextDNS from ATTFiber

Cannot ping / traceroute / nslookup  to NextDNS servers from ATT Home Fiber. I originally was having issues forwarding from my technitum dns servers. Troubleshooting finally determined it is connectivity between your ASN and ATT ASN.  Works from backup T-mobile connection.   It looks like a routing issue or ATT is blocking you guys.  As you are not accessible from outside  from the ATT Fiber device.   I am also going to try opening a case for ATT side but i dont think it will get  traction coming from a home user.

16 replies

null
    • NextDNs
    • 5 days ago
    • Reported - view

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

      • CHAOTICAFFINITY
      • 5 days ago
      • Reported - view

       hit submit on it already , but its basically  null routes once it hits the ATT network

      • NextDNs
      • 5 days ago
      • Reported - view

       please share the resulting URL

      • nhathuy1402kg
      • 5 days ago
      • Reported - view

       

      • CTL
      • 5 days ago
      • Reported - view

       

       

      here is output of report, ran again at 7pm CST:

       

      Resolvers:   68.94.156.9,68.94.157.9
      Testing IPv6 connectivity
        available: false
      Fetching https://test.nextdns.io
      Fetch error: Get "https://test.nextdns.io": dial tcp: lookup test.nextdns.io on 100.100.100.100:53: dial udp: lookup 68.94.156.9,68.94.157.9: 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 on 100.100.100.100:53: dial udp: lookup 68.94.156.9,68.94.157.9: 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 on 100.100.100.100:53: dial udp: lookup 68.94.156.9,68.94.157.9: no such host
      Fetching PoP name for anycast primary IPv4 (45.90.28.0)
      Fetch error: Get "https://dns.nextdns.io/info": dial tcp 45.90.28.0:443: connect: operation timed out
      Fetching PoP name for anycast secondary IPv4 (45.90.30.0)
      Fetch error: Get "https://dns.nextdns.io/info": dial tcp 45.90.30.0:443: connect: operation timed out
      Pinging PoPs
      error: Get "https://router.nextdns.io/?limit=10&stack=dual": dial tcp: lookup router.nextdns.io on 100.100.100.100:53: dial udp: lookup 68.94.156.9,68.94.157.9: no such host
      Traceroute error: lookup ipv4.dns1.nextdns.io on 100.100.100.100:53: dial udp: lookup 68.94.156.9,68.94.157.9: no such host
      Traceroute error: lookup ipv4.dns2.nextdns.io on 100.100.100.100:53: dial udp: lookup 68.94.156.9,68.94.157.9: no such host
      Traceroute for anycast primary IPv4 (45.90.28.0)
          1  162.203.124.1    2ms   1ms   1ms
          2  71.149.23.156    4ms   2ms   3ms
          3                   *     *     *
          4                   *     *     *
          5                   *     *     *
          6                   *     *     *
          7                   *     *     *
          8 62.115.139.131    *    10ms  12ms
          9  62.115.149.45   78ms  10ms  11ms
         10                   *     *     *
         11                   *     *     *
         12 155.138.250.114    8ms   8ms  10ms
         13                   *     *     *
         14                   *     *     *
         15                   *     *     *
         16                   *     *     *
         17                   *     *     *
         18                   *     *     *
         19                   *     *     *
         20                   *     *     *
      Traceroute for anycast secondary IPv4 (45.90.30.0)
          1  162.203.124.1    1ms   1ms   2ms
          2  71.149.23.156    3ms   3ms   3ms
          3                   *     *     *
          4                   *     *     *
          5                   *     *     *
          6                   *     *     *
          7                   *     *     *
          8  62.115.138.65   25ms  22ms  26ms
          9 62.115.164.226   28ms  26ms  26ms
         10 144.208.205.32   11ms  10ms  11ms
         11                   *     *     *
         12                   *     *     *
         13                   *     *     *
         14                   *     *     *
         15                   *     *     *
         16                   *     *     *
         17                   *     *     *
         18                   *     *     *
         19                   *     *     *
         20                   *     *     *

      • CTL
      • 4 days ago
      • Reported - view

        this is still broken as of 11/25 @ 11:06am CST. 

       

      Cannot ping either DNS server from ATT Fiber 45.90.28.156 or 45.90.30.156

      Testing with Tmobile hotspot works fine.

       

      Going on 3 days now of not being able to use this service. I've been a customer for awhile now but unfortunately after about another day of non-service I'll have to cancel my subscription and find something more reliable. 

    • CTL
    • 5 days ago
    • Reported - view

    I can confirm same issue. On ATTFiber, cannot ping any nextdns server or run a tracert. 

    Diag report:
    Resolvers:   68.94.156.9,68.94.157.9
    Testing IPv6 connectivity
      available: false
    Fetching https://test.nextdns.io
    Fetch error: Get "https://test.nextdns.io": dial tcp: lookup test.nextdns.io on 127.0.0.1:53: dial udp: lookup 68.94.156.9,68.94.157.9: 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 on 127.0.0.1:53: dial udp: lookup 68.94.156.9,68.94.157.9: 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 on 127.0.0.1:53: dial udp: lookup 68.94.156.9,68.94.157.9: no such host
    Fetching PoP name for anycast primary IPv4 (45.90.28.0)
    Fetch error: Get "https://dns.nextdns.io/info": dial tcp 45.90.28.0:443: connect: operation timed out
    Fetching PoP name for anycast secondary IPv4 (45.90.30.0)
    Fetch error: Get "https://dns.nextdns.io/info": dial tcp 45.90.30.0:443: connect: operation timed out
    Pinging PoPs
    error: Get "https://router.nextdns.io/?limit=10&stack=dual": dial tcp: lookup router.nextdns.io on 127.0.0.1:53: dial udp: lookup 68.94.156.9,68.94.157.9: no such host
    Traceroute error: lookup ipv4.dns1.nextdns.io on 127.0.0.1:53: dial udp: lookup 68.94.156.9,68.94.157.9: no such host
    Traceroute error: lookup ipv4.dns2.nextdns.io on 127.0.0.1:53: dial udp: lookup 68.94.156.9,68.94.157.9: no such host
    Traceroute for anycast primary IPv4 (45.90.28.0)
        1  162.203.124.1    2ms   0ms   1ms
        2  71.149.23.156    4ms   2ms   2ms
        3                   *     *     *
        4                   *     *     *
        5                   *     *     *
        6                   *     *     *
        7                   *     *     *
        8 62.115.136.118   10ms  10ms   9ms
        9  62.115.136.83   10ms  10ms   8ms
       10  62.115.149.45   13ms  11ms  17ms
       11                   *     *     *
       12                   *     *     *
       13 155.138.250.114    8ms  10ms  10ms
       14                   *     *     *
       15                   *     *     *
       16                   *     *     *
       17                   *     *     *
       18                   *     *     *
       19                   *     *     *
       20                   *     *     *
    Traceroute for anycast secondary IPv4 (45.90.30.0)
        1  162.203.124.1    2ms   0ms   1ms
        2  71.149.23.156    3ms   3ms   3ms
        3                   *     *     *
        4                   *     *     *
        5                   *     *     *
        6                   *     *     *
        7  192.205.37.10    9ms   9ms  10ms
        8 62.115.164.226   10ms  10ms  10ms
        9 144.208.205.32   11ms  11ms   9ms
       10                   *     *     *
       11                   *     *     *
       12                   *     *     *
       13                   *     *     *
       14                   *     *     *
       15                   *     *     *
       16                   *     *     *
       17                   *     *     *
       18                   *     *     *
       19                   *     *     *
       20                   *     *     *
    Do you want to send this report? [Y/n]: Y
    Optional email in case we need additional info
    Post unsuccessful: Post "https://api.nextdns.io/diagnostic": dial tcp: lookup api.nextdns.io on 127.0.0.1:53: dial udp: lookup 68.94.156.9,68.94.157.9: no such host
    Please report this issue on https://github.com/nextdns/diag

    • CHAOTICAFFINITY
    • 5 days ago
    • Reported - view

    It looks like as of  12:57 Central  nextdns is reachable via att fiber again

      • CTL
      • 5 days ago
      • Reported - view

       still down for me - South central USA on ATT Fiber

      • NextDNs
      • 4 days ago
      • Reported - view

       please try again

      • CTL
      • 4 days ago
      • Reported - view

      no luck, still cannot resolve test.nextdns.io, or ping 45.90.28.156, 45.90.30.156

      • CTL
      • 3 days ago
      • Reported - view

       Latest diag report:

       

      Resolvers:   68.94.156.9,68.94.157.9
      Testing IPv6 connectivity
        available: false
      Fetching https://test.nextdns.io
      Fetch error: Get "https://test.nextdns.io": dial tcp: lookup test.nextdns.io on 100.100.100.100:53: dial udp: lookup 68.94.156.9,68.94.157.9: 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 on 100.100.100.100:53: dial udp: lookup 68.94.156.9,68.94.157.9: 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 on 100.100.100.100:53: dial udp: lookup 68.94.156.9,68.94.157.9: no such host
      Fetching PoP name for anycast primary IPv4 (45.90.28.0)
      Fetch error: Get "https://dns.nextdns.io/info": dial tcp 45.90.28.0:443: connect: operation timed out
      Fetching PoP name for anycast secondary IPv4 (45.90.30.0)
      Fetch error: Get "https://dns.nextdns.io/info": dial tcp 45.90.30.0:443: connect: operation timed out
      Pinging PoPs
      error: Get "https://router.nextdns.io/?limit=10&stack=dual": dial tcp: lookup router.nextdns.io on 100.100.100.100:53: dial udp: lookup 68.94.156.9,68.94.157.9: no such host
      Traceroute error: lookup ipv4.dns1.nextdns.io on 100.100.100.100:53: dial udp: lookup 68.94.156.9,68.94.157.9: no such host
      Traceroute error: lookup ipv4.dns2.nextdns.io on 100.100.100.100:53: dial udp: lookup 68.94.156.9,68.94.157.9: no such host
      Traceroute for anycast primary IPv4 (45.90.28.0)
          1  162.203.124.1    0ms   0ms   2ms
          2  71.149.23.156    2ms   2ms   3ms
          3                   *     *     *
          4                   *     *     *
          5                   *     *     *
          6                   *     *     *
          7  129.250.8.213   10ms  10ms   9ms
          8  129.250.3.246   10ms  10ms  10ms
          9                   *     *     *
         10   128.241.7.63    9ms  10ms  32ms
         11                   *     *     *
         12                   *     *     *
         13 155.138.250.114    9ms   8ms   9ms
         14                   *     *     *
         15                   *     *     *
         16                   *     *     *
         17                   *     *     *
         18                   *     *     *
         19                   *     *     *
         20                   *     *     *
      Traceroute for anycast secondary IPv4 (45.90.30.0)
          1  162.203.124.1    0ms   2ms   0ms
          2  71.149.23.156    2ms   3ms   3ms
          3                   *     *     *
          4                   *     *     *
          5                   *     *     *
          6                   *     *     *
          7  129.250.8.213    9ms  10ms  11ms
          8  129.250.3.246   10ms  10ms  10ms
          9   129.250.3.59    9ms   8ms   9ms
         10 168.143.191.171    9ms  28ms   8ms
         11                   *     *     *
         12                   *     *     *
         13                   *     *     *
         14                   *     *     *
         15                   *     *     *
         16                   *     *     *
         17                   *     *     *
         18                   *     *     *
         19                   *     *     *
         20                   *     *     *

    • CTL
    • 3 days ago
    • Reported - view

     unfortunately this has gone on for 4 days now and is unacceptable. I've used NextDNS for 3 years with very few issues, but having an outage this bad isn't something I can live with, since I work remote and rely on my internet uptime to be consistent. 

     

    I've canceled my subscription and will be shifting to using Unbound DNS + Adguard plugin for OPNSENSE with an upstream TLS to cloudflare DNS. (or another DNS service later)

      • NextDNs
      • 3 days ago
      • Reported - view

       I understand. We’re still trying to understand what’s going on with this route.

    • Jason.47
    • 3 days ago
    • Reported - view

    This has been driving me crazy all week. Also on AT&T fiber out of Texas in the USA. NextDNS servers have been on and off unreachable all week. I've had to constantly swap my DNS settings out multiple times a day to keep my stuff online. I work from home so really hope this gets resolved or I'm going to have to cancel and bail on this service as well. I ran the diag tool but after it finished it threw this error:
    Post unsuccessful: status 400
    {"error":"0: instance.Test requires property \"Client\"\n"}

    Currently one of the two networks is reachable for me. The 45.90.28.0 network is reachable and the 45.90.30.0 network is not.

    I'm happy to help troubleshoot so let me know if there is someone I can reach out to privately to assist.

    Thanks,

    Jason

    • NextDNs
    • 2 days ago
    • Reported - view

    We are suspecting ATT Fiber is somewhat blocking our service for some unknown reason. What makes us think this is from the diag:

    1. our hostname (dns.nextdns.io) being blocked by their resolver
    2. both our anycast path, which are on different network paths and providers are unreachable, which is highly suspect

    We tried to reach them via different means with no success. Maybe you will have more success than us via their support chain… We'll keep trying.

Login to reply

Content aside

  • 1 Votes
  • 2 days agoLast active
  • 16Replies
  • 101Views
  • 5 Following