No response from NextDNS
Hi,
Since 11:26 (CEST) 29/10/2022, I'm getting no response from either of the NextDNS servers linked to my ip address.
45.90.28.158
45.90.30.158
are the two addresses I have tested.
I've a second profile that uses
45.90.28.63
45.90.30.63
but I've the same issue there also.
If I change to google public DNS 8.8.8.8, I am able to resolve names without issue.
A trace route to NextDNS times out after a few hops (first two hops edited as they are fixed public)
tracert 45.90.28.158
Tracing route to dns1.nextdns.io [45.90.28.158]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms a.b.c.d
2 4 ms 2 ms 3 ms w.x.y.z
3 7 ms 4 ms 3 ms bras-02str.bxl.be.edpnet.net [213.219.132.31]
4 5 ms 5 ms 6 ms router02.bruix.be.edpnet.net [212.71.11.53]
5 4 ms 4 ms 7 ms be6793.rcr21.bru01.atlas.cogentco.com [149.38.1.97]
6 9 ms 6 ms 8 ms be3676.ccr41.ams03.atlas.cogentco.com [154.54.57.177]
7 14 ms 7 ms 7 ms kpn.fra03.atlas.cogentco.com [130.117.14.10]
8 7 ms 8 ms 8 ms melbikomas-ic350933-adm-b10.ip.twelve99-cust.net [62.115.182.139]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
A trace route to Google public DNS works the whole way:
tracert 8.8.8.8
Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms a.b.c.d
2 4 ms 3 ms 3 ms w.x.y.z
3 7 ms 4 ms 5 ms bras-02str.bxl.be.edpnet.net [213.219.132.31]
4 6 ms 4 ms 4 ms router02.bruix.be.edpnet.net [212.71.11.53]
5 11 ms 11 ms 12 ms router01.adamtel.nl.edpnet.net [212.71.11.58]
6 13 ms 12 ms 11 ms 213.219.134.236.res.static.edpnet.net [213.219.134.236]
7 10 ms 11 ms 11 ms 142.251.70.127
8 11 ms 9 ms 10 ms 142.251.48.175
9 10 ms 11 ms 10 ms dns.google [8.8.8.8]
Trace complete.
Is there a support chat bot/email? I recall there used to be a chat bot, but it is gone now.
Does anyone have any suggestions?
Thanks in advance!
3 replies
-
To add:
If I re-link to the public IP I get from my 4G hotspot, the NextDNS ip addresses do respond. My ISP is the same for fixed and mobile. I do not believe it is an ISP specific issue as even when the trace route gets lost, it is well beyond my ISP's network (EDPnet)
-
Please try again.
-
Hi,
Yes, it is working again. Do you have any idea what might have caused this issue? I'm reluctant to switch back to NextDNS given that all 4 servers I was configured to try and resolve against were all inaccessiable at the same time.
Content aside
- Status Solved
- 2 yrs agoLast active
- 3Replies
- 144Views
-
2
Following