Timeout from Telia
Hi,
I have seen this problem increase in frequency over the last week - my devices are unable to connect to private DNS from a Telia connection in Sweden.
This is the output of the diagnostic tool:
selea@EdgeRouter-4:~$ sh -c 'sh -c "$(curl -s https://nextdns.io/diag)"'
Welcome to NextDNS network diagnostic tool.
This tool will download a small binary to capture latency and routing informatio n
regarding the connectivity of your network with NextDNS. In order to perform a
traceroute, root permission is required. You may therefore be asked to provide
your password for sudo.
The source code of this tool is available at https://github.com/nextdns/diag
Do you want to continue? (press enter to accept)
Testing IPv6 connectivity
available: false
Fetching https://test.nextdns.io
Fetch error: Get "https://test.nextdns.io": dial tcp 188.172.192.71:443: i/o timeout
Fetching PoP name for ultra low latency primary IPv4 (ipv4.dns1.nextdns.io)
Fetch error: Get "https://dns.nextdns.io/info": dial tcp 217.146.31.87:443: connect: connection timed out
Fetching PoP name for ultra low latency secondary IPv4 (ipv4.dns2.nextdns.io)
Fetch error: Get "https://dns.nextdns.io/info": dial tcp 86.106.103.153:443: connect: connection timed out
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: connection timed out
Fetching PoP name for anycast secondary IPv4 (45.90.30.0)
Why is this happening?
Would you please consider getting more IP's in different ASNs in order to mitigate routing-issues?
If a solution to this is not propose shortly, I will sadly have to find another solution...
5 replies
-
tracert:
Tracing route to dns1.nextdns.io [45.90.28.30] over a maximum of 30 hops: 1 5 ms 2 ms 2 ms 10.69.69.1 2 3 ms 3 ms 5 ms gw1-no286.tbcn.telia.com [81.235.16.1] 3 14 ms 10 ms 11 ms lid-c2-link.se.telia.net [81.228.91.100] 4 12 ms 12 ms 10 ms m-b-c1-link.se.telia.net [81.228.89.188] 5 45 ms 10 ms 46 ms m-b-peer1-link.se.telia.net [81.228.84.95] 6 53 ms 10 ms 52 ms kbn-b1-link.ip.twelve99.net [62.115.123.158] 7 114 ms 116 ms 96 ms kbn-bb2-link.ip.twelve99.net [62.115.138.112] 8 22 ms 19 ms 19 ms s-bb2-link.ip.twelve99.net [62.115.139.172] 9 19 ms 18 ms 19 ms s-b3-link.ip.twelve99.net [62.115.118.109] 10 22 ms 19 ms 20 ms m247-ic336858-s-b10.ip.twelve99-cust.net [62.115.163.50] 11 20 ms 24 ms 20 ms vlan2904.as04.stk1.se.m247.com [212.103.51.117] 12 19 ms 19 ms 20 ms interxion-sto3.edge.sto01.se.misaka.io [45.11.107.151] 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete.
-
traceroute (WSL):
3 gw1-no286.tbcn.telia.com (81.235.16.1) 5.183 ms 5.162 ms 5.156 ms 4 lid-c2-link.se.telia.net (81.228.91.100) 12.643 ms 12.640 ms 13.015 ms 5 m-b-c1-link.se.telia.net (81.228.89.188) 12.441 ms 12.434 ms 12.430 ms 6 m-b-peer1-link.se.telia.net (81.228.84.95) 12.458 ms 11.199 ms 9.990 ms 7 kbn-b1-link.ip.twelve99.net (62.115.123.158) 11.182 ms 15.350 ms 15.276 ms 8 kbn-bb1-link.ip.twelve99.net (62.115.143.6) 25.027 ms 31.155 ms * 9 s-bb2-link.ip.twelve99.net (62.115.139.172) 22.391 ms 22.383 ms 22.373 ms 10 s-b3-link.ip.twelve99.net (62.115.118.107) 22.368 ms 22.360 ms s-b3-link.ip.twelve99.net (62.115.118.109) 22.352 ms 11 m247-ic351270-s-b3.ip.twelve99-cust.net (62.115.183.87) 30.940 ms 30.933 ms m247-ic336858-s-b10.ip.twelve99-cust.net (62.115.163.50) 22.330 ms 12 vlan2909.as04.stk1.se.m247.com (212.103.51.241) 30.669 ms vlan2904.as04.stk1.se.m247.com (212.103.51.117) 30.920 ms 24.908 ms 13 interxion-sto3.edge.sto01.se.misaka.io (45.11.107.151) 24.878 ms 24.871 ms 24.757 ms 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * *
-
Can you please DM your IP so we can investigate?
-
I have sent the details in a PM
-
I had the same issue this morning aswell.
Content aside
- 2 yrs agoLast active
- 5Replies
- 120Views
-
2
Following