0

Vietnam (Asia) is routed to anycast Spain (Europe)

Recently, I use CLI on Ubuntu and find that CLI is not connecting to utralow server anymore. When I tested anycast server it was routed to Spain, the speed of resolution and connection was extremely slow.

In Southeast Asia (with Vietnam), the nearest and fastest anycast servers are Hong Kong and Singapore. Hopefully this problem will be fixed soon, the slow speed will affect the user experience in the region. Thank you!

https://nextdns.io/diag/6f5be9a0-9d93-11eb-b893-a7953b5d735d

----

With IPv6, I check the network has IPv6, the server utralow does not have?

Testing IPv6 connectivity
  available: true
Fetching https://test.nextdns.io
  status: ok
  client: 115.73.153.38
  protocol: UDP
  dest IP: 45.90.30.0
  server: anexia-hkg-1
Fetching PoP name for ultra low latency primary IPv4 (ipv4.dns1.nextdns.io)
  anexia-han: 26.169ms
Fetching PoP name for ultra low latency secondary IPv4 (ipv4.dns2.nextdns.io)
  greencloud-han: 31.811ms
Fetching PoP name for anycast primary IPv4 (45.90.28.0)
  zepto-mad: 190.493ms
Fetching PoP name for anycast secondary IPv4 (45.90.30.0)
  anexia-hkg: 178.092ms
Fetching PoP name for ultra low latency primary IPv6 (ipv6.dns1.nextdns.io)
Fetch error: Get "https://dns.nextdns.io/info": dial tcp: lookup ipv6.dns1.nextd
ns.io: no such host
Fetching PoP name for ultra low latency secondary IPv6 (ipv6.dns2.nextdns.io)
Fetch error: Get "https://dns.nextdns.io/info": dial tcp: lookup ipv6.dns2.nextd
ns.io: no such host
Fetching PoP name for anycast primary IPv6 (2a07:a8c0::)
  zepto-hkg: 56.718ms
Fetching PoP name for anycast secondary IPv6 (2a07:a8c1::)
  vultr-tyo: 105.394ms
Pinging PoPs
  greencloud-han (IPv6): 24.857ms
  greencloud-han: 24.834ms
  anexia-han: 26.752ms
  vultr-sin: 51.972ms
  premiumrdp-bkk: 53ms
  zepto-sin: 53.896ms
  vultr-sin (IPv6): 54.757ms
  anexia-sin (IPv6): 60.762ms
  premiumrdp-kul: 58ms
  bangmod-bkk: 65.652ms
  serverwala-kul: 65ms
  gsl-sin: 92ms
  zepto-sin (IPv6): 96.103ms
  anexia-sin: 104.929ms
  gsl-sin (IPv6): 201ms
Traceroute for ultra low latency primary IPv4 (203.162.172.59)
    1    192.168.1.1    9ms   3ms   3ms
    2 125.235.251.199    3ms   5ms   4ms
    3    115.79.0.84    7ms   6ms   3ms
    4   27.68.209.45   13ms  32ms  53ms
    5   27.68.236.34    7ms   6ms   6ms
    6  113.171.7.221   28ms  28ms  28ms
    7 113.171.14.250   30ms  30ms  29ms
    8                   *     *     *
    9  113.171.5.230   28ms  27ms  27ms
   10 203.162.169.98   69ms  66ms  28ms
   11 203.162.172.59   28ms  29ms  29ms
Traceroute for ultra low latency secondary IPv4 (103.199.17.192)
    1    192.168.1.1    5ms   1ms   1ms
    2 125.235.251.199    4ms   3ms   3ms
    3    115.79.0.84   28ms   4ms   4ms
    4   27.68.209.61   15ms   4ms   4ms
    5   27.68.209.53   35ms  34ms  36ms
    6   27.68.255.77   36ms  30ms  31ms
    7  27.68.229.150   28ms  29ms  30ms
    8  171.244.2.226   28ms  28ms  29ms
    9  171.244.2.202   31ms  28ms  28ms
   10   171.244.2.58   28ms  25ms  26ms
   11 103.199.17.192   31ms  29ms  29ms
Traceroute for anycast primary IPv4 (45.90.28.0)
    1    192.168.1.1    3ms   1ms   4ms
    2 125.235.251.199    3ms   3ms   3ms
    3    115.79.0.84   23ms  30ms  16ms
    4   27.68.209.45   29ms  27ms  14ms
    5  27.68.237.210    8ms   9ms  12ms
    6   27.68.255.54   44ms  39ms  39ms
    7   27.68.244.27   37ms  36ms  36ms
    8 203.131.248.245   79ms  78ms  78ms
    9  129.250.6.124   78ms  79ms  85ms
   10   129.250.6.92   81ms  78ms  78ms
   11 203.131.242.154   37ms  36ms  37ms
   12  45.11.107.175   38ms  37ms  38ms
   13     45.90.28.0   40ms  48ms  37ms
Traceroute for anycast secondary IPv4 (45.90.30.0)
    1    192.168.1.1    6ms   1ms   1ms
    2 125.235.251.199    6ms   3ms   5ms
    3    115.79.0.84    4ms   3ms   4ms
    4   27.68.209.45   10ms  15ms  15ms
    5  27.68.237.210    7ms   9ms  16ms
    6   27.68.250.76   38ms  36ms  36ms
    7                   *     *     *
    8     45.90.30.0  184ms 179ms 183ms
  Traceroute error: lookup ipv6.dns1.nextdns.io: no such host
  Traceroute error: lookup ipv6.dns2.nextdns.io: no such host
Traceroute for anycast primary IPv6 (2a07:a8c0::)
    1 2402:800:633c:45a5:1da3:bcdb:8b12:b788    3ms   7ms   1ms
    2 2402:800:633c::1    9ms  22ms   5ms
    3 2402:800:63ff:e::e:1   94ms  12ms  24ms
    4 2402:800:1130:56::1    6ms  11ms   5ms
    5   27.68.254.51   42ms  39ms  39ms
    6   27.68.253.51   41ms  39ms  39ms
    7 2402:800:1130:243::1   42ms  35ms  37ms
    8 2001:218:7000:5000::749   36ms  38ms  35ms
    9 2001:218:0:2000::181   39ms  36ms  37ms
   10 2001:218:0:2000::12d   37ms  37ms  45ms
   11 2001:218:6000:5000::1aa   56ms  56ms  56ms
   12 2a02:6ea0:8:1230:5390::2   65ms  64ms  64ms
   13    2a07:a8c0::   57ms  55ms  55ms
Traceroute for anycast secondary IPv6 (2a07:a8c1::)
    1 2402:800:633c:45a5:1da3:bcdb:8b12:b788    3ms   1ms   1ms
    2 2402:800:633c::1   16ms   9ms   2ms
    3 2402:800:63ff:e::d:1    3ms   3ms   5ms
    4 2402:800:1130:56::1    6ms   *    34ms
    5   27.68.254.51   47ms  93ms 114ms
    6   27.68.253.51   96ms 116ms  95ms
    7 2402:800:1130:243::1    *    91ms   *
    8 2001:218:7000:5000::749   38ms  38ms  44ms
    9 2001:218:0:2000::181   36ms  36ms  36ms
   10 2001:218:0:2000::189   81ms  77ms  77ms
   11 2001:218:0:2000::101   77ms  78ms  77ms
   12 2001:218:2000:5000::566  101ms 102ms 138ms
   13 2001:19f0:fc00::a47:2ea  110ms 110ms 110ms
   14 2001:19f0:fc00::a47:d6  102ms 102ms 102ms
   15                   *     *     *
   16    2a07:a8c1::  135ms 128ms 117ms

https://nextdns.io/diag/1f7ca610-9d96-11eb-b893-a7953b5d735d

9replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • You are connected using UDP (IP linking). If you installed CLI, you are not using it.

    Like
      • BigDargon
      • BigDargon
      • 4 wk ago
      • Reported - view

      Olivier Poitrey It seems you are misunderstanding, 2 completely different problems.  
       

      Issue 1, I am talking about a DoH connection and anycast is routing to a very far server.  Exactly here is Spain (Europe), while I'm in Vietnam (Asia)

       

      Second, utralow's IPv6 server has no search results.

       

      Please see the 2 analysis links I have posted above.  Thank you!

      Like
    • BigDargon if you use DoH you will be on ultralow, so on a closer pop. This pop has no v6 yet but it doesn’t really matter, it will still resolve v6 addresses.

      Like 1
    • BigDargon for the madrid issue, can you please show the output if traceroute -T 45.90.28.0 (from the linux box)

      Like
      • BigDargon
      • BigDargon
      • 4 wk ago
      • Reported - view

      Olivier Poitrey Here to 45.90.28.0

      traceroute to 45.90.28.0 (45.90.28.0), 30 hops max, 60 byte packets
       1  192.168.1.1 (192.168.1.1)  0.502 ms  0.424 ms  0.377 ms
       2  125.235.251.199.adsl.viettel.vn (125.235.251.199)  1.186 ms  1.141 ms  1.098 ms
       3  adsl.viettel.vn (115.79.0.84)  8.533 ms  8.698 ms  8.666 ms
       4  localhost (27.68.209.45)  11.943 ms  11.901 ms  11.857 ms
       5  localhost (27.68.237.210)  4.898 ms  4.858 ms  4.816 ms
       6  localhost (27.68.255.54)  34.581 ms  36.787 ms  39.024 ms
       7  localhost (27.68.244.27)  36.215 ms  34.950 ms  34.826 ms
       8  xe-2-2-3-xcr1.hke.cw.net (195.89.113.21)  72.348 ms 203.131.248.245 (203.131.248.245)  75.996 ms xe-2-2-3-xcr1.hke.cw.net (195.89.113.21)  73.247 ms
       9  ae4-xcr1.hkg.cw.net (195.2.10.97)  252.360 ms  252.888 ms  252.779 ms
      10  ae-2.r02.tkokhk01.hk.bb.gin.ntt.net (129.250.6.94)  75.552 ms ae49.xcr1.mar.cw.net (195.2.20.241)  245.279 ms  245.189 ms
      11  195.2.31.242 (195.2.31.242)  252.863 ms  253.027 ms 203.131.242.154 (203.131.242.154)  35.653 ms
      12  fwd-1.eq2.hkg12.hk.misaka.io (45.11.107.175)  35.486 ms 217.161.95.147 (217.161.95.147)  187.156 ms fwd-1.eq2.hkg12.hk.misaka.io (45.11.107.175)  34.511 ms
      13  fwd-1.in2.mad01.es.misaka.io (45.11.107.144)  187.163 ms * *
      14  * * *
      15  * * *
      16  * * *
      17  * * *
      18  * * *
      19  * * *
      20  * * *
      21  * * *
      22  * * *
      23  * * *
      24  * * *
      25  * * *
      26  * * *
      27  * * *
      28  * * *
      29  * * *
      30  * * *
      

      And here to 45.90.30.0

      traceroute to 45.90.30.0 (45.90.30.0), 30 hops max, 60 byte packets
       1  192.168.1.1 (192.168.1.1)  0.523 ms  0.439 ms  0.396 ms
       2  125.235.251.199.adsl.viettel.vn (125.235.251.199)  1.359 ms  1.325 ms  1.285 ms
       3  adsl.viettel.vn (115.79.0.84)  1.977 ms  1.945 ms  2.188 ms
       4  localhost (27.68.209.45)  8.809 ms  8.764 ms  8.729 ms
       5  localhost (27.68.237.210)  4.883 ms  4.850 ms  5.071 ms
       6  localhost (27.68.250.76)  33.562 ms  35.235 ms  33.784 ms
       7  * * *
       8  * * *
       9  * * *
      10  * * *
      11  * * *
      12  * * *
      13  * * *
      14  * * *
      15  * * *
      16  * * *
      17  * * *
      18  * * *
      19  * * *
      20  * * *
      21  * * *
      22  * * *
      23  * * *
      24  * * *
      25  * * *
      26  * * *
      27  * * *
      28  * * *
      29  * * *
      30  * * *
      
      Like
      • BigDargon
      • BigDargon
      • 3 wk ago
      • Reported - view

      Olivier Poitrey After 7 days still routing to Spain

      traceroute to 45.90.28.0 (45.90.28.0), 30 hops max, 60 byte packets
       1  LINKSYS-JERRY (192.168.1.1)  0.507 ms  0.449 ms  0.404 ms
       2  125.235.251.199.adsl.viettel.vn (125.235.251.199)  1.237 ms  1.168 ms  1.130 ms
       3  adsl.viettel.vn (115.79.0.84)  1.935 ms  1.894 ms  2.033 ms
       4  localhost (27.68.209.45)  5.419 ms  5.383 ms  5.364 ms
       5  localhost (27.68.237.210)  4.929 ms  4.842 ms  4.794 ms
       6  localhost (27.68.255.54)  39.811 ms  39.736 ms  34.856 ms
       7  localhost (27.68.244.27)  30.109 ms  31.974 ms  31.744 ms
       8  xe-2-2-3-xcr1.hke.cw.net (195.89.113.21)  70.888 ms 203.131.248.245 (203.131.248.245)  75.930 ms  74.758 ms
       9  ae4-xcr1.hkg.cw.net (195.2.10.97)  253.550 ms ae-14.r27.tkokhk01.hk.bb.gin.ntt.net (129.250.5.254)  78.947 ms ae-13.r26.tkokhk01.hk.bb.gin.ntt.net (129.250.6.124)  77.759 ms
      10  ae-2.r02.tkokhk01.hk.bb.gin.ntt.net (129.250.6.94)  75.628 ms ae-1.r02.tkokhk01.hk.bb.gin.ntt.net (129.250.6.92)  70.495 ms  70.463 ms
      11  203.131.242.154 (203.131.242.154)  31.811 ms 195.2.31.242 (195.2.31.242)  250.614 ms 203.131.242.154 (203.131.242.154)  33.492 ms
      12  217.161.95.147 (217.161.95.147)  186.171 ms fwd-1.eq2.hkg12.hk.misaka.io (45.11.107.175)  32.799 ms  31.105 ms
      13  fwd-1.in2.mad01.es.misaka.io (45.11.107.144)  185.633 ms *  185.569 ms
      14  * * *
      15  * * *
      16  * * *
      17  * * *
      18  * * *
      19  * * *
      20  * * *
      21  * * *
      22  * * *
      23  * * *
      24  * * *
      25  * * *
      26  * * *
      27  * * *
      28  * * *
      29  * * *
      30  * * *
      
      Like
    • BigDargon please check again

      Like 1
      • BigDargon
      • BigDargon
      • 3 wk ago
      • Reported - view

      Olivier Poitrey Checked. Looks like the routing was working fine. Thank you for your support!

      traceroute to 45.90.28.0 (45.90.28.0), 30 hops max, 60 byte packets
       1  LINKSYS-JERRY (192.168.1.1)  0.517 ms  0.429 ms  0.379 ms
       2  125.235.251.199.adsl.viettel.vn (125.235.251.199)  1.238 ms  1.199 ms  1.162 ms
       3  adsl.viettel.vn (115.79.0.84)  1.998 ms  2.223 ms  1.923 ms
       4  localhost (27.68.209.45)  18.790 ms  18.765 ms  18.724 ms
       5  localhost (27.68.237.210)  4.999 ms  4.972 ms  4.937 ms
       6  localhost (27.68.255.54)  39.469 ms  41.333 ms  38.732 ms
       7  localhost (27.68.244.27)  30.186 ms  30.340 ms  31.757 ms
       8  203.131.248.245 (203.131.248.245)  75.839 ms  74.024 ms  74.489 ms
       9  ae-14.r27.tkokhk01.hk.bb.gin.ntt.net (129.250.5.254)  72.434 ms ae-13.r26.tkokhk01.hk.bb.gin.ntt.net (129.250.6.124)  81.062 ms ae-14.r27.tkokhk01.hk.bb.gin.ntt.net (129.250.5.254)  73.181 ms
      10  ae-1.r02.tkokhk01.hk.bb.gin.ntt.net (129.250.6.92)  70.635 ms  72.518 ms ae-2.r02.tkokhk01.hk.bb.gin.ntt.net (129.250.6.94)  75.718 ms
      11  203.131.242.154 (203.131.242.154)  36.005 ms  35.920 ms  35.855 ms
      12  fwd-1.eq2.hkg12.hk.misaka.io (45.11.107.175)  30.665 ms  30.580 ms  32.699 ms
      13  * * *
      14  * * *
      15  * * *
      16  * * *
      17  * * *
      18  * * *
      19  * * *
      20  * * *
      21  * * *
      22  * * *
      23  * * *
      24  * * *
      25  * * *
      26  * * *
      27  * * *
      28  * * *
      29  * * *
      30  * * *
      
      Like
  • When the device started, CLI connected to the utralow server. After some time, CLI reconnects to use anycast server. This is the log

    Apr 15 17:35:40 ODROID-JERRY systemd[1]: Started NextDNS DNS53 to DoH proxy..
    Apr 15 17:35:41 ODROID-JERRY nextdns[696]: Starting NextDNS 1.11.0/linux on localhost:53
    Apr 15 17:35:41 ODROID-JERRY nextdns[696]: Listening on TCP/[::1]:53
    Apr 15 17:35:41 ODROID-JERRY nextdns[696]: Listening on TCP/127.0.0.1:53
    Apr 15 17:35:41 ODROID-JERRY nextdns[696]: Listening on UDP/127.0.0.1:53
    Apr 15 17:35:41 ODROID-JERRY nextdns[696]: Listening on UDP/[::1]:53
    Apr 15 17:35:46 ODROID-JERRY nextdns[696]: Activating
    Apr 15 17:35:51 ODROID-JERRY nextdns[696]: Network change detected: eth0 up
    Apr 15 17:35:51 ODROID-JERRY nextdns[696]: Connected 203.162.172.59:443 (con=24ms tls=37ms, TLS13)
    Apr 15 17:35:51 ODROID-JERRY nextdns[696]: Switching endpoint: https://dns.nextdns.io.#203.162.172.59,103.199.17.192
    Apr 15 19:22:40 ODROID-JERRY nextdns[696]: Connected 203.162.172.59:443 (con=25ms tls=58ms, TLS13)
    Apr 15 19:24:06 ODROID-JERRY nextdns[696]: Connected 203.162.172.59:443 (con=24ms tls=49ms, TLS13)
    Apr 15 19:26:20 ODROID-JERRY nextdns[696]: Connected 103.199.17.192:443 (con=23ms tls=52ms, TLS13)
    Apr 15 19:29:35 ODROID-JERRY nextdns[696]: Connected 203.162.172.59:443 (con=24ms tls=42ms, TLS13)
    Apr 15 19:32:39 ODROID-JERRY nextdns[696]: Connected 103.199.17.192:443 (con=23ms tls=42ms, TLS13)
    Apr 15 19:33:30 ODROID-JERRY nextdns[696]: Connected 203.162.172.59:443 (con=25ms tls=49ms, TLS13)
    Apr 15 19:36:19 ODROID-JERRY nextdns[696]: Connected 203.162.172.59:443 (con=24ms tls=52ms, TLS13)
    Apr 15 19:36:19 ODROID-JERRY nextdns[696]: Connected 203.162.172.59:443 (con=25ms tls=54ms, TLS13)
    Apr 15 19:36:19 ODROID-JERRY nextdns[696]: Switching endpoint: https://dns.nextdns.io.#103.199.17.192,203.162.172.59
    Apr 15 22:23:30 ODROID-JERRY nextdns[696]: Connected 103.199.17.192:443 (con=23ms tls=36ms, TLS13)
    Apr 15 22:23:31 ODROID-JERRY nextdns[696]: Connected 45.90.28.0:443 (con=188ms tls=200ms, TLS13)
    Apr 15 22:23:31 ODROID-JERRY nextdns[696]: Switching endpoint: https://dns.nextdns.io.#45.90.28.0,2a07:a8c0::
    Apr 16 07:16:20 ODROID-JERRY nextdns[696]: Connected 45.90.28.0:443 (con=35ms tls=58ms, TLS13)
    Apr 16 09:04:32 ODROID-JERRY nextdns[696]: Connected 45.90.28.0:443 (con=35ms tls=48ms, TLS13)
    Apr 16 09:10:02 ODROID-JERRY nextdns[696]: Connected 45.90.28.0:443 (con=36ms tls=52ms, TLS13)
    Apr 16 09:11:38 ODROID-JERRY nextdns[696]: Connected 45.90.28.0:443 (con=188ms tls=209ms, TLS13)
    Apr 16 09:12:38 ODROID-JERRY nextdns[696]: Connected 45.90.28.0:443 (con=188ms tls=210ms, TLS13)
    
    Like
Like Follow
  • 3 wk agoLast active
  • 9Replies
  • 95Views
  • 2 Following