search

AdguardTeam / AdGuardDNS

Public DNS resolver that protects you from ad trackers
https://adguard-dns.io/
GNU Affero General Public License v3.0
744 stars 61 forks source link

Routing Issue - Indonesia Being Routed to Germany Instead of Singapore #672

Open mahara opened 9 months ago

mahara commented 9 months ago

Platform

Windows

Protocol

DNS-over-HTTPS DNS-over-QUIC

Do you use AdGuard app?

Yes I am

Your configuration

I'm using both latest AdGuard VPN version 2.1.5 (1021) and AdGuard version 7.1.4 on Windows 11.

DNS server set to default AdGuard DNS (94.140.14.14) using DoH or DoQ in both applications.

Traceroute to AdGuard DNS

tracert 94.140.14.14

Tracing route to dns.adguard.com [94.140.14.14]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  router.asus.com [192.168.50.1]
  2     2 ms     1 ms     1 ms  192.168.1.1
  3     3 ms     2 ms     2 ms  10.213.64.1
  4     3 ms     2 ms     3 ms  125.160.0.62
  5     5 ms     4 ms     4 ms  125.160.0.61
  6    11 ms    11 ms    14 ms  180.240.190.77
  7    12 ms    11 ms    11 ms  180.240.190.77
  8   197 ms   198 ms   204 ms  180.240.192.233
  9   189 ms   189 ms   189 ms  ae27-0.fra10.core-backbone.com [5.56.19.101]
 10   184 ms   183 ms   185 ms  core-backbone.cdn77.com [5.56.19.238]
 11   184 ms   185 ms   184 ms  vl213.fra-mc1-dist-2.cdn77.com [185.229.188.123]
 12   191 ms   191 ms   191 ms  dns.adguard.com [94.140.14.14]

Trace complete.

Issue Details

I connect to Singapore server in AdGuard VPN.

The AdGuard Test (https://adguard.com/en/test.html) shows the correct DNS server: Singapore.

You are using "Default" AdGuard DNS configuration
Protocol: "DNS"
Server: "dns2-dp-sg-5"

But the problem is the traceroute and actual connection seems being directed to Germany (Frankfurt) (https://ipinfo.io/185.229.188.123) instead of Singapore as it becomes noticeably much slower than usual.

Expected Behavior

Traceroute and actual connection should be correctly directed to Singapore server as shown by the following traceroute to Cloudflare (1.1.1.1).

tracert 1.1.1.1

Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  router.asus.com [192.168.50.1]
  2     2 ms     1 ms     1 ms  192.168.1.1
  3     3 ms     2 ms     2 ms  10.213.64.1
  4     3 ms     3 ms     3 ms  125.160.0.62
  5     4 ms     4 ms     4 ms  125.160.0.61
  6    10 ms    10 ms    16 ms  180.240.190.77
  7    11 ms    10 ms    10 ms  180.240.190.77
  8    18 ms    17 ms    17 ms  180.240.205.80
  9    23 ms    24 ms    25 ms  162.158.160.248
 10    19 ms    18 ms    19 ms  172.70.140.3
 11    13 ms    14 ms    12 ms  one.one.one.one [1.1.1.1]

Trace complete.

Actual Behavior

The DNS server and actual connection being directed to Germany instead, making connection speed becomes noticeably much slower than usual.

Screenshots

No response

Additional Information

This seems to coincidentally happen since I updated to AdGuard VPN app to the latest version 2.1.5 from 2.1.4. Not sure if that's related.

mahara commented 9 months ago

OK, not sure what has just been changed under the hood, but the routing now seems to work normally ONLY when VPN is connected, but not when VPN is NOT connected. I only updated the AdGuard VPN to the latest release version, 2.1.6 (1028).

It's still being routed to Germany (Frankfurt) (https://ipinfo.io/185.229.188.121) when VPN is not connected.

Here's the latest trace route and ping data.

AdGuard VPN connected to Singapore server

tracert 94.140.14.14

Tracing route to dns.adguard.com [94.140.14.14]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6    17 ms    17 ms    17 ms  dns.adguard.com [94.140.14.14]

Trace complete.
ping 94.140.14.14 -n 30

Pinging 94.140.14.14 with 32 bytes of data:
Reply from 94.140.14.14: bytes=32 time=17ms TTL=42
Reply from 94.140.14.14: bytes=32 time=16ms TTL=42
Reply from 94.140.14.14: bytes=32 time=17ms TTL=42
Reply from 94.140.14.14: bytes=32 time=18ms TTL=42
Reply from 94.140.14.14: bytes=32 time=16ms TTL=42
Reply from 94.140.14.14: bytes=32 time=17ms TTL=42
Reply from 94.140.14.14: bytes=32 time=17ms TTL=42
Reply from 94.140.14.14: bytes=32 time=19ms TTL=42
Reply from 94.140.14.14: bytes=32 time=18ms TTL=42
Reply from 94.140.14.14: bytes=32 time=19ms TTL=42
Reply from 94.140.14.14: bytes=32 time=17ms TTL=42
Reply from 94.140.14.14: bytes=32 time=18ms TTL=42
Reply from 94.140.14.14: bytes=32 time=17ms TTL=42
Reply from 94.140.14.14: bytes=32 time=18ms TTL=42
Reply from 94.140.14.14: bytes=32 time=17ms TTL=42
Reply from 94.140.14.14: bytes=32 time=17ms TTL=42
Reply from 94.140.14.14: bytes=32 time=18ms TTL=42
Reply from 94.140.14.14: bytes=32 time=18ms TTL=42
Reply from 94.140.14.14: bytes=32 time=18ms TTL=42
Reply from 94.140.14.14: bytes=32 time=18ms TTL=42
Reply from 94.140.14.14: bytes=32 time=17ms TTL=42
Reply from 94.140.14.14: bytes=32 time=17ms TTL=42
Reply from 94.140.14.14: bytes=32 time=17ms TTL=42
Reply from 94.140.14.14: bytes=32 time=18ms TTL=42
Reply from 94.140.14.14: bytes=32 time=18ms TTL=42
Reply from 94.140.14.14: bytes=32 time=18ms TTL=42
Reply from 94.140.14.14: bytes=32 time=18ms TTL=42
Reply from 94.140.14.14: bytes=32 time=17ms TTL=42
Reply from 94.140.14.14: bytes=32 time=18ms TTL=42
Reply from 94.140.14.14: bytes=32 time=16ms TTL=42

Ping statistics for 94.140.14.14:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 16ms, Maximum = 19ms, Average = 17ms

AdGuard VPN not connected

tracert 94.140.14.14

Tracing route to dns.adguard.com [94.140.14.14]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  router.asus.com [192.168.50.1]
  2     2 ms     1 ms     1 ms  192.168.1.1
  3     4 ms     3 ms     4 ms  10.213.64.1
  4     3 ms     2 ms     2 ms  125.160.0.62
  5     4 ms     2 ms     2 ms  125.160.0.61
  6    17 ms    16 ms    16 ms  180.240.190.77
  7    15 ms    15 ms    14 ms  180.240.190.77
  8   187 ms   186 ms   187 ms  180.240.192.233
  9   161 ms   160 ms   161 ms  ae27-0.fra10.core-backbone.com [5.56.19.101]
 10   169 ms   168 ms   168 ms  core-backbone.cdn77.com [5.56.19.238]
 11   170 ms   171 ms   170 ms  vl211.fra-mc1-dist-1.cdn77.com [185.229.188.121]
 12   175 ms   174 ms   175 ms  dns.adguard.com [94.140.14.14]

Trace complete.
ping 94.140.14.14 -n 30

Pinging 94.140.14.14 with 32 bytes of data:
Reply from 94.140.14.14: bytes=32 time=176ms TTL=54
Reply from 94.140.14.14: bytes=32 time=175ms TTL=54
Reply from 94.140.14.14: bytes=32 time=175ms TTL=54
Reply from 94.140.14.14: bytes=32 time=175ms TTL=54
Reply from 94.140.14.14: bytes=32 time=176ms TTL=54
Reply from 94.140.14.14: bytes=32 time=176ms TTL=54
Reply from 94.140.14.14: bytes=32 time=176ms TTL=54
Reply from 94.140.14.14: bytes=32 time=176ms TTL=54
Reply from 94.140.14.14: bytes=32 time=176ms TTL=54
Reply from 94.140.14.14: bytes=32 time=176ms TTL=54
Reply from 94.140.14.14: bytes=32 time=176ms TTL=54
Reply from 94.140.14.14: bytes=32 time=177ms TTL=54
Reply from 94.140.14.14: bytes=32 time=177ms TTL=54
Reply from 94.140.14.14: bytes=32 time=176ms TTL=54
Reply from 94.140.14.14: bytes=32 time=177ms TTL=54
Reply from 94.140.14.14: bytes=32 time=177ms TTL=54
Reply from 94.140.14.14: bytes=32 time=176ms TTL=54
Reply from 94.140.14.14: bytes=32 time=176ms TTL=54
Reply from 94.140.14.14: bytes=32 time=177ms TTL=54
Reply from 94.140.14.14: bytes=32 time=177ms TTL=54
Reply from 94.140.14.14: bytes=32 time=177ms TTL=54
Reply from 94.140.14.14: bytes=32 time=177ms TTL=54
Reply from 94.140.14.14: bytes=32 time=177ms TTL=54
Reply from 94.140.14.14: bytes=32 time=176ms TTL=54
Reply from 94.140.14.14: bytes=32 time=176ms TTL=54
Reply from 94.140.14.14: bytes=32 time=176ms TTL=54
Reply from 94.140.14.14: bytes=32 time=177ms TTL=54
Reply from 94.140.14.14: bytes=32 time=177ms TTL=54
Reply from 94.140.14.14: bytes=32 time=176ms TTL=54
Reply from 94.140.14.14: bytes=32 time=177ms TTL=54

Ping statistics for 94.140.14.14:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 175ms, Maximum = 177ms, Average = 176ms
ivanjx commented 3 months ago

mine:

[admin@MikroTik] > /tool/traceroute dns.adguard.com
Columns: ADDRESS, LOSS, SENT, LAST, AVG, BEST, WORST, STD-DEV
 #  ADDRESS          LOSS   SENT  LAST     AVG    BEST   WORST  STD-DEV
 1  192.168.1.1      0%        3  0.7ms    0.7    0.7    0.8    0      
 2  10.143.0.1       0%        3  1.1ms    1.1    1.1    1.2    0      
 3  180.252.1.222    66.7%     3  timeout  1.3    1.3    1.3    0      
 4  180.252.3.13     0%        3  1.5ms    3.5    1.5    7.4    2.7    
 5  192.168.144.26   0%        3  1.4ms    1.3    1.3    1.4    0      
 6  192.168.144.25   0%        3  2ms      2.1    1.8    2.4    0.2    
 7                   100%      3  timeout                              
 8  180.240.190.109  33.3%     3  16.2ms   16.3   16.2   16.4   0.1    
 9  180.240.196.2    0%        3  193.5ms  194.1  193.5  195.2  0.8    
10  5.56.19.101      0%        3  189.7ms  189.8  189.7  190    0.1    
11  169.150.195.68   0%        3  190.5ms  190.9  190.5  191.2  0.4    
12  169.150.194.51   0%        2  196.9ms  194.5  192    196.9  2.5    
13  94.140.14.14     0%        2  192.5ms  192.3  192.1  192.5  0.2

image