0

I'm blocked connecting to NextDNS?

I've this weird issue which is remarkably similar to the issue listed below. I Cannot ping or curl ipv4.dns1.nextdns.io. If I use a vpn it works flawlessly but from my own network i always get timeouts, Is my IP being blocked for whatever reason.

 

root@<>:/root# curl https://ipv4.dns1.nextdns.io/info -m 10 --interface tun0
{"locationName": " Amsterdam, Netherlands", "pop": "anexia-ams", "rtt": 61451}

root@<>:/root# curl https://ipv4.dns1.nextdns.io/info -m 10
curl: (28) Connection timed out after 10001 milliseconds
root@kate:/root#

root@<>:/root# ping ipv4.dns1.nextdns.io
PING ipv4-dns1.steering.nextdns.io (188.172.219.167) 56(84) bytes of data.
^C
--- ipv4-dns1.steering.nextdns.io ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4073ms

<local macbook>
ping ipv4.dns1.nextdns.io
PING ipv4-dns1.steering.nextdns.io (93.189.61.195): 56 data bytes
64 bytes from 93.189.61.195: icmp_seq=0 ttl=55 time=8.437 ms
64 bytes from 93.189.61.195: icmp_seq=1 ttl=55 time=13.072 ms
^C
--- ipv4-dns1.steering.nextdns.io ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 8.437/10.755/13.072/2.317 ms

 

 

similar post:
https://help.nextdns.io/t/60h5x3b/im-blocked-connecting-to-nextdns

1 reply

null
    • R_P_M
    • 1 mth ago
    • Reported - view

    You’re getting a different IP address for ipv4.dns1.nextdns.io when using the vpn.

    Try ping with vpn connection again but this time use the IP address result of first. 

    ping -c5 188.172.219.167

    (-c # controls the number of pings)

Login to reply

Content aside

  • 1 mth agoLast active
  • 1Replies
  • 45Views
  • 2 Following