0

my.nextdns.io and ping.nextdns.io not resolving

So, for the past couple of hours now, I am unable to resolve my.nextdns.io on my phone (which uses mobile data) and ping.nextdns.io but am able to resolve test.nextdns.io.

I have tried using both the Private DNS (DoT) and using the official NextDNS apps (DoH) as well. 

Surprisingly, I am able to resolve my.nextdns.io on my desktop.

I think this could have something to do with ipv4 (laptop - wifi) and ipv6 (mobile data) addressees. 

Please look into the same.

3 replies

null
    • iamtheanon
    • 3 yrs ago
    • Reported - view

    Details of ping on mobile data using ipv6 (do-blr).

     

    $ ping my.nextdns.io

    PING cname.vercel-dns.com (76.76.21.21) 56(84) bytes of data.

    From 172.26.40.64: icmp_seq=1 Time to live exceeded

    From 172.26.40.64: icmp_seq=21 Time to live exceeded

    --- cname.vercel-dns.com ping statistics ---

    146 packets transmitted, 0 received, +2 errors, 100% packet loss, time 168541ms

    • iamtheanon
    • 3 yrs ago
    • Reported - view

    From my mac as well using mobile hotspot running NextDNS CLI on Big Sur.  

    (base) ykgmacair-MacBook-Air ~ % ping my.nextdns.io
PING cname.vercel-dns.com (76.76.21.21): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
Request timeout for icmp_seq 10
Request timeout for icmp_seq 11
Request timeout for icmp_seq 12
Request timeout for icmp_seq 13
Request timeout for icmp_seq 14
Request timeout for icmp_seq 15
Request timeout for icmp_seq 16
Request timeout for icmp_seq 17
Request timeout for icmp_seq 18
Request timeout for icmp_seq 19
Request timeout for icmp_seq 20
Request timeout for icmp_seq 21
^C
--- cname.vercel-dns.com ping statistics ---
23 packets transmitted, 0 packets received, 100.0% packet loss

     

    Also the trace-route with the NextDNS CLI for my.nextdns.io is as follows: 

    traceroute to cname.vercel-dns.com (76.76.21.21), 64 hops max, 52 byte packets
1  192.168.225.1 (192.168.225.1)  3.911 ms  4.096 ms  6.081 ms
2  * * *
3  56.8.157.77 (56.8.157.77)  51.560 ms
    10.72.244.165 (10.72.244.165)  36.405 ms
    56.8.157.69 (56.8.157.69)  59.281 ms
4  192.168.53.193 (192.168.53.193)  108.555 ms
    192.168.53.195 (192.168.53.195)  113.292 ms
    192.168.53.199 (192.168.53.199)  163.516 ms
5  192.168.53.194 (192.168.53.194)  67.713 ms  47.490 ms
    192.168.53.196 (192.168.53.196)  60.717 ms
6  172.26.76.245 (172.26.76.245)  26.765 ms  36.903 ms  52.938 ms
7  172.26.76.227 (172.26.76.227)  42.874 ms
    172.26.76.226 (172.26.76.226)  38.293 ms  49.237 ms
8  192.168.53.174 (192.168.53.174)  40.041 ms  549.745 ms
    192.168.53.178 (192.168.53.178)  212.791 ms
9  192.168.53.179 (192.168.53.179)  217.014 ms  37.008 ms
    192.168.53.177 (192.168.53.177)  73.130 ms
10  * * *
11  * * *
12  * * *
13  * * *
14  172.16.16.10 (172.16.16.10)  48.960 ms * *
15  172.16.92.145 (172.16.92.145)  64.576 ms
    172.26.40.7 (172.26.40.7)  75.130 ms *
16  * * *
17  * * *
18  * * *
19  * * *
20  * 172.26.40.65 (172.26.40.65)  43.649 ms *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  172.16.16.10 (172.16.16.10)  41.837 ms * *
27  * 172.16.92.145 (172.16.92.145)  38.973 ms *
28  * * *
29  * * *
30  * * *
31  * * *
32  172.16.16.10 (172.16.16.10)  1514.277 ms *
    172.26.40.65 (172.26.40.65)  33.468 ms
33  172.26.40.7 (172.26.40.7)  66.149 ms  61.968 ms *
34  * * *
35  * * *
36  *^C
    • iamtheanon
    • 3 yrs ago
    • Reported - view

    Working fine now for the past 2 hours. 

Login to reply

Content aside

  • 3 yrs agoLast active
  • 3Replies
  • 242Views
  • 2 Following