0

verizon fios routing issue

having a routing issue can't seem to access nextdns just today.

 

nextdns.io/diag -

Resolvers:   68.237.161.12,71.243.0.12
Testing IPv6 connectivity
  available: false
Fetching https://test.nextdns.io
Fetch error: Get "https://test.nextdns.io": dial tcp: lookup test.nextdns.io on 192.168.1.16:53: dial udp: lookup 68.237.161.12,71.243.0.12: 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 192.168.1.16:53: dial udp: lookup 68.237.161.12,71.243.0.12: 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 192.168.1.16:53: dial udp: lookup 68.237.161.12,71.243.0.12: 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)

 

directly from router - 

 traceroute to 45.90.28.0 (45.90.28.0), 64 hops max, 40 byte packetsTTLAS#HostAddressProbes

1 AS701 lo0-100.NYCMNY-VFTTP-372.verizon-gni.net 173.56.84.1 2.135 ms
2 AS701 T0-8-0-9.BSTNMA-LCR-21.verizon-gni.net 100.41.196.248 2.920 ms
3 AS0 0.ae2.BR2.NYC4.ALTER.NET 140.222.229.93 2.762 ms
4 AS701 verizon.com.customer.alter.net 152.179.72.42 2.854 ms
5 AS2914 ae-2.r20.nwrknj03.us.bb.gin.ntt.net 129.250.3.50 3.438 ms
6 AS2914 ae-1.r00.nwrknj03.us.bb.gin.ntt.net 129.250.6.53 4.084 ms
7 AS2914 ce-0-2-0-3.r00.nwrknj03.us.ce.gin.ntt.net

1 reply

null
    • charles.2
    • 9 mths ago
    • Reported - view

    Resolvers:   68.237.161.12,71.243.0.12
    Testing IPv6 connectivity
      available: false
    Fetching https://test.nextdns.io
    Fetch error: Get "https://test.nextdns.io": dial tcp: lookup test.nextdns.io on 192.168.1.16:53: dial udp: lookup 68.237.161.12,71.243.0.12: 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 192.168.1.16:53: dial udp: lookup 68.237.161.12,71.243.0.12: 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 192.168.1.16:53: dial udp: lookup 68.237.161.12,71.243.0.12: 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 192.168.1.16:53: dial udp: lookup 68.237.161.12,71.243.0.12: no such host
    Traceroute error: lookup ipv4.dns1.nextdns.io on 192.168.1.16:53: dial udp: lookup 68.237.161.12,71.243.0.12: no such host
    Traceroute error: lookup ipv4.dns2.nextdns.io on 192.168.1.16:53: dial udp: lookup 68.237.161.12,71.243.0.12: no such host
    Traceroute for anycast primary IPv4 (45.90.28.0)
        1    173.56.84.1    9ms   2ms   3ms
        2 100.41.196.248    3ms   4ms   2ms
        3   140.222.1.59    3ms   8ms  11ms
        4  152.179.72.42    3ms   3ms   4ms
        5   129.250.3.50    3ms   3ms   3ms
        6   129.250.6.53    5ms   4ms   4ms
        7  128.241.12.86   41ms   4ms   4ms

Login to reply

Content aside

  • 9 mths agoLast active
  • 1Replies
  • 38Views
  • 1 Following