AdGuardDNS
AdGuardDNS copied to clipboard
AdguardTeam
AdGuard DNS not using the nearest server — Singapore
Hi, I’m located in Singapore but I’m being routed to Japan servers instead.
DNS Server Location Screenshot
Not sure how networking work, and how geographically it deem Japan server as having the least network hops. Here's my traceroute results;
Traceroute result to 94.140.14.14
traceroute to 94.140.14.14 (94.140.14.14), 64 hops max, 52 byte packets
1 192.168.1.254 (192.168.1.254) 2.320 ms 2.020 ms 4.176 ms
2 bb219-75-48-254.singnet.com.sg (219.75.48.254) 4.968 ms 3.869 ms 3.328 ms
3 202.166.123.130 (202.166.123.130) 3.721 ms 3.849 ms 3.936 ms
4 202.166.123.129 (202.166.123.129) 9.326 ms 3.580 ms 3.515 ms
5 ae8-0.qt-cr03.singnet.com.sg (202.166.121.101) 8.371 ms 12.907 ms 4.655 ms
6 ae13-0.tp-cr03.singnet.com.sg (202.166.120.109) 3.303 ms 4.013 ms 3.446 ms
7 ae4-0.tp-er03.singnet.com.sg (202.166.123.70) 4.243 ms 19.256 ms 4.941 ms
8 203.208.145.233 (203.208.145.233) 3.877 ms
203.208.191.197 (203.208.191.197) 13.148 ms
203.208.191.113 (203.208.191.113) 7.383 ms
9 203.208.158.190 (203.208.158.190) 4.482 ms 4.695 ms 4.736 ms
10 203.208.171.109 (203.208.171.109) 4.103 ms 4.087 ms 4.372 ms
11 203.208.152.34 (203.208.152.34) 36.108 ms
203.208.183.250 (203.208.183.250) 14.779 ms 6.102 ms
12 203.208.171.229 (203.208.171.229) 39.153 ms
203.208.173.153 (203.208.173.153) 45.059 ms 45.616 ms
13 203.208.154.14 (203.208.154.14) 39.172 ms 39.131 ms
63-218-205-9.static.pccwglobal.net (63.218.205.9) 45.895 ms
14 63-218-205-9.static.pccwglobal.net (63.218.205.9) 40.653 ms 41.171 ms 38.962 ms
15 63-218-205-9.static.pccwglobal.net (63.218.205.9) 41.291 ms 40.958 ms
hundredge0-0-0-9.clbr01.tok02.pccwbtn.net (63.218.250.193) 77.806 ms
16 hundredge0-0-0-1.clbr01.tok02.pccwbtn.net (63.218.250.177) 81.961 ms
ssi-labo.gi0-0-0-3.843.br04.tok01.pccwbtn.net (63.216.242.46) 77.938 ms 77.909 ms
17 hundredge0-0-0-1.clbr01.tok02.pccwbtn.net (63.218.250.177) 82.391 ms
ssi-labo.gi0-0-0-3.843.br04.tok01.pccwbtn.net (63.216.242.46) 82.819 ms 130.358 ms
18 * * ssi-labo.gi0-0-0-3.843.br04.tok01.pccwbtn.net (63.216.242.46) 95.061 ms
19 * * *
20 * dns.adguard.com (94.140.14.14) 524.822 ms 307.451 ms
Traceroute result to 94.140.15.15
traceroute to 94.140.15.15 (94.140.15.15), 64 hops max, 52 byte packets
1 192.168.1.254 (192.168.1.254) 2.836 ms 0.911 ms 1.335 ms
2 bb219-75-48-254.singnet.com.sg (219.75.48.254) 4.266 ms 4.233 ms 5.974 ms
3 202.166.123.130 (202.166.123.130) 4.377 ms 3.565 ms 4.449 ms
4 202.166.123.129 (202.166.123.129) 2.757 ms 2.401 ms 2.394 ms
5 ae8-0.qt-cr03.singnet.com.sg (202.166.121.101) 7.441 ms 2.593 ms 2.543 ms
6 ae13-0.tp-cr03.singnet.com.sg (202.166.120.109) 3.977 ms 3.317 ms 3.257 ms
7 ae4-0.tp-er03.singnet.com.sg (202.166.123.70) 3.402 ms 3.891 ms 5.326 ms
8 203.208.145.233 (203.208.145.233) 4.309 ms
203.208.191.197 (203.208.191.197) 4.921 ms
203.208.191.113 (203.208.191.113) 16.928 ms
9 203.208.158.190 (203.208.158.190) 5.824 ms
203.208.153.186 (203.208.153.186) 18.158 ms 4.730 ms
10 203.208.171.109 (203.208.171.109) 7.745 ms 5.246 ms 5.945 ms
11 203.208.183.250 (203.208.183.250) 4.995 ms
203.208.166.17 (203.208.166.17) 38.303 ms
203.208.183.250 (203.208.183.250) 6.078 ms
12 203.208.152.194 (203.208.152.194) 38.570 ms
203.208.171.229 (203.208.171.229) 38.216 ms
203.208.171.242 (203.208.171.242) 44.924 ms
13 203.208.151.94 (203.208.151.94) 45.767 ms
203.208.166.62 (203.208.166.62) 45.596 ms
203.208.154.14 (203.208.154.14) 39.317 ms
14 63-218-205-9.static.pccwglobal.net (63.218.205.9) 43.028 ms 39.495 ms 45.950 ms
15 hundredge0-0-0-1.clbr01.tok02.pccwbtn.net (63.218.250.177) 77.939 ms 86.769 ms
hundredge0-0-0-9.clbr01.tok02.pccwbtn.net (63.218.250.193) 77.317 ms
16 hundredge0-0-0-1.clbr01.tok02.pccwbtn.net (63.218.250.177) 81.012 ms
hundredge0-0-0-9.clbr01.tok02.pccwbtn.net (63.218.250.193) 77.736 ms 76.673 ms
17 ssi-labo.gi0-0-0-3.843.br04.tok01.pccwbtn.net (63.216.242.46) 82.962 ms 77.113 ms *
18 * * *
19 * * *
20 * * *
21 * * dns.adguard.com (94.140.15.15) 80.569 ms
I'm also experiencing similar issues. I am located in NY and there's an Adguard DNS resolver close to me however, I'm being routed to a server in Japan which is causing significant latency issues.
https://github.com/AdguardTeam/AdGuardDNS/issues/99#issuecomment-774338938
I'm also experiencing similar issues. I am located in NY and there's an Adguard DNS resolver close to me however, I'm being routed to a server in Japan which is causing significant latency issues.
I live in NY as well and am being routed to Japan! The routing that AdGuard does is completely F'ed up, glad to know I am not alone though. Their decision to use shortest number of hops is fundamentally flawed. Yes, 3 hops at 200 ms (with timeouts mind you) is shorter than 10 hops at 10 ms but that doesn't make it faster.
6 16 ms 14 ms 15 ms bu-ether16.nycmny837aw-bcr00.tbone.rr.com [66.109.6.74]
7 13 ms 12 ms 15 ms 0.ae1.pr1.nyc20.tbone.rr.com [107.14.17.218]
8 13 ms 14 ms 18 ms 66.109.9.18
9 184 ms 180 ms 180 ms HundredGE0-0-0-0.clbr01.tok02.pccwbtn.net [63.218.250.173]
10 183 ms 183 ms 183 ms ssi-labo.gi0-0-0-3.843.br04.tok01.pccwbtn.net [63.216.242.46]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 186 ms 185 ms 186 ms dns.adguard.com [94.140.15.15]
Hello, this is an old issue with adguard dns, sometimes the routing is working well but now, since the day they changed to the news addresses, i have still the same problem. The place I live in is in Europe, I use a dual stack ipv4/ipv6 connection, from my home i can ping Frankfurt 22ms, Amsterdam 12ms, Paris 14ms, London 13ms..my ipv6 dns requests are redirected to Amsterdam with 8 hops, (this is great) BUT all my ipv4 dns requests are redirected to USA 89ms 11 hops.. This is happening with my belgian/dutch ISP, i have no issue with my mobile provider..
Update: As of recent, I'm being routed to Amsterdam (dns2-dp-ams-2). I'm still located in NY.
Is there a way to choose your own server location?
As per my knowledge, route taken by ip packets from one destination to another completely depends on original internet server provider of tier-1 isp that u r connected to. It's not Adguard's fault. Report routing errors to isp.
I am located in India. Nearest adguard dns is Singapore. But i always got connected to NY server. So i complained to local isp who in turn uses Tata Communication as tier-1 isp, and said "ask Tata to change routing table". Within 1 week tier-1 isp of India changed their routing tables and the shortest path to SG got selected. Enjoying lower latency now
As per my knowledge, route taken by ip packets from one destination to another completely depends on original internet server provider of tier-1 isp that u r connected to. It's not Adguard's fault. Report routing errors to isp.
I am located in India. Nearest adguard dns is Singapore. But i always got connected to NY server. So i complained to local isp who in turn uses Tata Communication as tier-1 isp, and said "ask Tata to change routing table". Within 1 week tier-1 isp of India changed their routing tables and the shortest path to SG got selected.
Enjoying lower latency now
Impressive that Tata took into account your request. Won't happen here is Europe.
I have some issues with Google and YTM because their routing table are wrong but their so called specialists told me nothing was wrong on their side. Such arrogant Google engeneers.
