Adguard DNS (beta)

+ 1.

 

Anycast is connecting me to the US East server even tho the US West server has slightly faster ping times

US West:
Pinging 104.156.231.95 with 32 bytes of data:
Reply from 104.156.231.95: bytes=32 time=53ms TTL=51
Reply from 104.156.231.95: bytes=32 time=53ms TTL=51
Reply from 104.156.231.95: bytes=32 time=49ms TTL=51
Reply from 104.156.231.95: bytes=32 time=48ms TTL=51

Ping statistics for 104.156.231.95:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 53ms, Average = 50ms

US East:
Pinging 45.76.4.21 with 32 bytes of data:
Reply from 45.76.4.21: bytes=32 time=56ms TTL=52
Reply from 45.76.4.21: bytes=32 time=58ms TTL=51
Reply from 45.76.4.21: bytes=32 time=58ms TTL=52
Reply from 45.76.4.21: bytes=32 time=60ms TTL=51

Ping statistics for 45.76.4.21:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 56ms, Maximum = 60ms, Average = 58ms

Tracert:
Tracing route to 176-103-130-130.flops.ru [176.103.130.130]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms router.asus.com [192.168.1.1]
2 11 ms 11 ms 10 ms 96.120.12.137
3 16 ms 19 ms 11 ms ae-204-sur02.denver.co.denver.comcast.net [162.151.38.229]
4 13 ms 10 ms 9 ms ae-10-sur01.denver.co.denver.comcast.net [68.86.128.101]
5 16 ms 10 ms 10 ms ae-20-ar01.denver.co.denver.comcast.net [68.86.128.169]
6 17 ms 11 ms 12 ms be-33652-cr02.1601milehigh.co.ibone.comcast.net [68.86.92.121]
7 19 ms 15 ms 14 ms be-11721-cr02.denver.co.ibone.comcast.net [68.86.86.77]
8 38 ms 36 ms 37 ms be-10517-cr02.350ecermak.il.ibone.comcast.net [68.86.85.169]
9 58 ms 55 ms 55 ms be-10305-cr02.newyork.ny.ibone.comcast.net [68.86.85.201]
10 57 ms 54 ms 61 ms be-10368-pe01.111eighthave.ny.ibone.comcast.net [68.86.84.218]
11 57 ms 69 ms 54 ms 50.242.150.38
12 69 ms 66 ms 58 ms vl50-br1.pnj1.choopa.net [66.55.144.146]
13 * * * Request timed out.
14 61 ms 56 ms 55 ms ethernet1-2-2:1-c12-11-b5-2.pnj1.choopa.net [108.61.65.178]
15 * * * Request timed out.
16 58 ms 55 ms 54 ms 176-103-130-130.flops.ru [176.103.130.130]

Trace complete.

 

Might be the same issue as with EU server.

Let me please explain how it works. The thing is that anycast is not a geo-location or ping-related thing. Basically, you'll get routed to a server with the shortest route from your provider (see traceroute command output). So, in some cases, you might end up connected to a server located somewhere far from you despite living in 100 meters from the closest on. However, according to the Sydney server load, it is not as bad as the EU one, quite a few people get routed to it.

Please show me the traceroute output, I'll check what's wrong with it.

 

C:\Windows\system32>tracert 176.103.130.130

Tracing route to 176-103-130-130.flops.ru [176.103.130.130]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 12 ms 25 ms 38 ms 144.130.210.209
4 33 ms 26 ms 9 ms bundle-ether10.exi-core10.melbourne.telstra.net [203.50.11.109]
5 101 ms 52 ms 24 ms bundle-ether12.chw-core10.sydney.telstra.net [203.50.11.124]
6 29 ms 28 ms 20 ms bundle-ether1.oxf-gw11.sydney.telstra.net [203.50.6.93]
7 28 ms 37 ms 40 ms bundle-ether1.sydo-core03.sydney.reach.com [203.50.13.98]
8 19 ms 22 ms 27 ms i-0-1-0-17.sydo-core04.bi.telstraglobal.net [202.84.222.62]
9 213 ms 226 ms 217 ms i-34.eqnx-core01.bx.telstraglobal.net [202.84.136.33]
10 276 ms 275 ms 279 ms i-0-4-0-10.ny8a-core01.bi.telstraglobal.net [202.84.136.93]
11 277 ms 280 ms 276 ms i-0-1-0-1.tnrt-core01.bi.telstraglobal.net [202.84.137.65]
12 342 ms 337 ms 343 ms i-0-1-2-0.ulhc-core01.bx.telstraglobal.net [202.84.249.26]
13 344 ms 344 ms 346 ms 202.84.178.14
14 * * * Request timed out.
15 359 ms 355 ms 375 ms xe000-18.RT.IXC.MSK.RU.retn.net [46.46.128.101]
16 * * * Request timed out.
17 355 ms 361 ms 356 ms 176-103-130-130.flops.ru [176.103.130.130]

Trace complete.

 

So both of you are routed to the russian server. The same issue as with the EU server then.

We'll try to resolve it today. I'll report back when it's done.

 

Guys, the issue with EU servers seems to be resolved. Not yet sure about Sydney, could you please check?

 

And now you get routed to the EU server

 

here is mine
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\Windows\system32>tracert 176.103.130.130

Tracing route to 176-103-130-130.flops.ru [176.103.130.130]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 8 ms 8 ms 8 ms 144.130.210.209
4 10 ms 9 ms 10 ms bundle-ether10.exi-core10.melbourne.telstra.net [203.50.11.109]
5 23 ms 22 ms 22 ms bundle-ether12.chw-core10.sydney.telstra.net [203.50.11.124]
6 22 ms 22 ms 22 ms bundle-ether1.oxf-gw11.sydney.telstra.net [203.50.6.93]
7 22 ms 22 ms 22 ms bundle-ether1.sydo-core03.sydney.reach.com [203.50.13.98]
8 22 ms 22 ms 22 ms i-0-1-0-17.sydo-core04.bi.telstraglobal.net [202.84.222.62]
9 160 ms 159 ms 159 ms i-0-4-0-29.1wlt-core02.bx.telstraglobal.net [202.84.136.209]
10 159 ms 158 ms 159 ms i-93.tlot02.bi.telstraglobal.net [202.84.253.86]
11 161 ms 162 ms 162 ms gtt-peer.tlot02.pr.telstraglobal.net [134.159.63.182]
12 202 ms 203 ms 203 ms xe-0-1-1.cr0-sjc2.ip4.gtt.net [141.136.110.14]
13 203 ms 202 ms 203 ms as20473-gw.sjc20.ip4.gtt.net [69.22.143.238]
14 204 ms 203 ms 203 ms vl501-ds1-b5-yd36.sjc1.choopa.net [45.32.142.6]
15 * * * Request timed out.
16 201 ms 201 ms 201 ms 176-103-130-130.flops.ru [176.103.130.130]

Trace complete.

 

Something changed recently here for me in the US as well. Ping times went from awesome to lousy.

 

I can judge by the servers load only, and it seems to be rather good in the US.

Can't say the same for Sydney yet, @jimmytim also is routed to the EU server.

 

I added the 176.103.130.130 and 176.103.130.131 ips to my DNS space on my router. I went on to the adguard dns page and it tells me that I am not using the dns servers...

 

Using both a Sagemcom router and Ubiquiti Nanostation M2 Access Point at different locations. Both don't detect the dns change

 

The only guess is that you've set something wrong. Have you tried setting it in the device settings?

 

Yes, on both devices. Even when I change the DNS on my iPhone when connected to my home Wi-Fi and go to the adguard dns page it doesn't detect it is being used.

 

Could you please show me the output of the "traceroute 176.103.130.130" command? Maybe one of the servers is wrongly configured, we'd better check which one exactly.

 

How do I traceroute it? Also, if it helps in located in New York City

 

Run Command Prompt as Administrator and enter this command - tracert 176.103.130.130

 

Here are my tracert results:
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>tracert 176.103.130.130

Tracing route to 176-103-130-130.flops.ru [176.103.130.130]
over a maximum of 30 hops:

1 13 ms 4 ms 3 ms openrg.home [192.168.1.1]
2 16 ms 12 ms 11 ms 10.240.161.73
3 14 ms 12 ms 18 ms 67.59.230.89
4 28 ms 16 ms 15 ms ool-4353dda4.dyn.optonline.net [67.83.221.164]
5 17 ms 17 ms 13 ms 64.15.4.56
6 29 ms 29 ms 30 ms 64.15.1.72
7 * * * Request timed out.
8 20 ms 17 ms 25 ms vl39-br1.pnj1.choopa.net [66.55.144.149]
9 * * * Request timed out.
10 18 ms 19 ms 17 ms ethernet1-2-2:1-c12-11-b5-2.pnj1.choopa.net [108.61.65.178]
11 * * * Request timed out.
12 16 ms 16 ms 16 ms 176-103-130-130.flops.ru [176.103.130.130]

Trace complete.

C:\WINDOWS\system32>

 

g'day avatar
any magical update on the sydney servers yet?

 

Seems to be okay, you're getting routed to NJ, it is the closest to you.

We tried a few things. Any change in the traceroute output?

 

Here is mine. Am I going to NJ? Does not appear so. Let me know.

Code:

Tracing route to 176-103-130-130.flops.ru [176.103.130.130]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     3 ms     4 ms     3 ms  lo0-100.PHLAPA-VFTTP-376.verizon-gni.net [96.245.165.1]
  3     9 ms     6 ms     6 ms  B3376.PHLAPA-LCR-21.verizon-gni.net [100.41.213.88]
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6    12 ms    11 ms    10 ms  0.ae1.GW11.IAD8.ALTER.NET [140.222.233.3]
  7    13 ms    14 ms    12 ms  teliasonera-gw.customer.alter.net [204.148.11.138]
  8    12 ms    11 ms    12 ms  ash-bb4-link.telia.net [213.155.130.58]
  9    85 ms    84 ms    85 ms  ldn-bb2-link.telia.net [62.115.116.69]
 10    89 ms    89 ms    89 ms  adm-bb4-link.telia.net [213.155.136.93]
 11    92 ms    90 ms    91 ms  adm-b3-link.telia.net [62.115.137.145]
 12     *       95 ms    94 ms  vultr-ic-313751-adm-b3.c.telia.net [62.115.58.194]
 13   109 ms   110 ms   114 ms  vl502-ds2-j2-r5-19-16.ams1.choopa.net [173.199.113.70]
 14     *        *        *     Request timed out.
 15    92 ms    92 ms    91 ms  176-103-130-130.flops.ru [176.103.130.130]

Trace complete.

 

Nope, you're getting routed to the EU server.

 

That is what I thought. Anyway you can look into it? I am in PA and getting routed overseas lol. Let me know what you need. Thanks!