Ad blocking not working. Ping to nextdns shows error.
-
+1 on this. No ads getting blocked now.
Is some issue going on??
-
+1 same issue with me too.
https://help.nextdns.io/t/35h56l4/primary-dns-server-is-not-responding
Paid subscribers have no proper customer support.
@NextDNS
-
I am running it on raspberry pi and today morning it switched to the anycast IP. It was connected to ultralow before that. Looks like the problem started after that
Jan 25 06:27:56 raspi nextdns[582]: Connected 217.146.10.59:443 (con=6ms tls=19ms, TCP, TLS13) Jan 25 06:29:33 raspi nextdns[582]: Connected 217.146.10.59:443 (con=6ms tls=15ms, TCP, TLS13) Jan 25 06:31:39 raspi nextdns[582]: Connected 103.127.29.198:443 (con=6ms tls=20ms, TCP, TLS13) Jan 25 06:33:57 raspi nextdns[582]: Connected 103.127.29.198:443 (con=5ms tls=16ms, TCP, TLS13) Jan 25 06:34:00 raspi nextdns[582]: Connected 45.90.28.0:443 (con=54ms tls=449ms, TCP, TLS13) Jan 25 06:34:00 raspi nextdns[582]: Switching endpoint: https://dns.nextdns.io#45.90.28.0,2a07:a8c0:: Jan 25 06:34:58 raspi nextdns[582]: Connected 45.90.28.0:443 (con=56ms tls=234ms, TCP, TLS13) Jan 25 06:35:57 raspi nextdns[582]: Connected 45.90.28.0:443 (con=199ms tls=61ms, TCP, TLS13) Jan 25 06:37:10 raspi nextdns[582]: Connected 45.90.28.0:443 (con=53ms tls=67ms, TCP, TLS13) Jan 25 06:39:40 raspi nextdns[582]: Connected 45.90.28.0:443 (con=97ms tls=88ms, TCP, TLS13)nextdns
-
https://nextdns.io/diag/f54a20e0-7da3-11ec-9cc9-719bc9b4a5ed
the diag is also very poor. I am based in Delhi and it shows my ultralow in Dubai now. It used to be microhost or anexia in Delhi
@NextDNS
-
+1
Doesn’t work on Airtel Wi-Fi, but works perfectly on Jio 4G.
-
@NextDNS Will there be any response from your side?? Silence is not helping
-
We are looking into this issue. Are you all on airtel?
-
NextDNS Yes, I’m on Airtel fiber.
-
NextDNS Yes Airtel fiber AS24560
-
NextDNS I am on Gazon Fiber
-
NextDNS I'm on Hathway and BBNL broadband
-
NextDNS I am on ATT U-verse and experiencing this issue.
-
For those who can't ping our anycast IP, please send your IP over direct message.
-
NextDNS Is there any reference ticket number
Edit: BTW anycast IP is pingable but no access to ultralow. At the same time no ads blocking happening
-
NextDNS Any update on the solution for the above issue?
-
Nagendra @NextDNS
For me it is now connecting to ultralow but adblocking is very poor.
Happened yesterday at 4PM
Jan 26 14:36:50 raspi nextdns[582]: Connected 45.90.28.0:443 (con=60ms tls=72ms, TCP, TLS13) Jan 26 14:52:21 raspi nextdns[582]: Connected 45.90.28.0:443 (con=60ms tls=88ms, TCP, TLS13) Jan 26 15:57:03 raspi nextdns[582]: Connected 45.90.28.0:443 (con=97ms tls=224ms, TCP, TLS13) Jan 26 16:01:28 raspi nextdns[582]: Connected 45.90.28.0:443 (con=62ms tls=80ms, TCP, TLS13) Jan 26 16:01:29 raspi nextdns[582]: Connected 103.127.29.198:443 (con=5ms tls=336ms, TCP, TLS13) Jan 26 16:01:29 raspi nextdns[582]: Switching endpoint: https://dns.nextdns.io#103.127.29.198,217.146.10.59 Jan 26 16:12:19 raspi nextdns[582]: Connected 217.146.10.59:443 (con=4ms tls=18ms, TCP, TLS13) Jan 26 16:29:36 raspi nextdns[582]: Connected 217.146.10.59:443 (con=6ms tls=14ms, TCP, TLS13) Jan 26 16:30:15 raspi nextdns[582]: Connected 217.146.10.59:443 (con=5ms tls=17ms, TCP, TLS13) Jan 26 16:35:00 raspi nextdns[582]: Connected 103.127.29.198:443 (con=5ms tls=9ms, TCP, TLS13) Jan 26 17:05:45 raspi nextdns[582]: Connected 103.127.29.198:443 (con=6ms tls=16ms, TCP, TLS13)
-
-
@NextDNS The issues are resolved for me now. Low latency and blocking are both working fine.
