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 8 ms <1 ms <1 ms 192.168.0.1 2 * * * Request timed out. 3 36 ms 27 ms 37 ms 144.130.208.209 4 37 ms 27 ms 38 ms bundle-ether2.chw-edge901.sydney.telstra.net [203.50.11.103] 5 32 ms 35 ms 37 ms aap1135271.lnk.telstra.net [139.130.209.230] 6 * 51 ms 37 ms lag41.sglebinte01.aapt.net.au [202.10.14.199] 7 41 ms 29 ms 41 ms lag30.sclarinte01.aapt.net.au [202.10.14.197] 8 32 ms 28 ms 76 ms aapt.sy4.nsw.coloau.au.net.au [210.9.30.254] 9 33 ms 37 ms 37 ms dom.as20473-xe-0-3-0.cr2.s1.nsw.au.coloau.net.au [103.52.116.168] 10 41 ms 38 ms 38 ms dom.as20473.cr2.s1.nsw.au.coloau.net.au [103.52.116.169] 11 33 ms 37 ms 38 ms vl800-ds1-b5-r1121.aus1.choopa.net [103.43.73.130] 12 * * * Request timed out. 13 39 ms 38 ms 37 ms 176-103-130-130.flops.ru [176.103.130.130] Trace complete. C:\WINDOWS\system32>
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 9 ms 144.130.210.209 4 9 ms 8 ms 8 ms aaptli6.lnk.telstra.net [139.130.41.106] 5 20 ms 18 ms 20 ms po9.mflindist02.aapt.net.au [202.10.14.32] 6 18 ms 19 ms 17 ms te2-1-110.mflindist01.aapt.net.au [202.10.12.136] 7 20 ms 19 ms 18 ms te0-3-4-0.mflincore01.aapt.net.au [202.10.12.11] 8 20 ms 19 ms 19 ms bu2.sglebcore01.aapt.net.au [202.10.10.72] 9 19 ms 17 ms 20 ms po12.sclardist02.aapt.net.au [202.10.12.4] 10 26 ms 31 ms 29 ms 5-1-1.sclarinte01.aapt.net.au [203.131.60.33] 11 19 ms 45 ms 19 ms aapt.sy4.nsw.coloau.au.net.au [210.9.30.254] 12 19 ms 19 ms 48 ms dom.as20473-xe-0-3-0.cr2.s1.nsw.au.coloau.net.au [103.52.116.168] 13 20 ms 19 ms 19 ms dom.as20473.cr2.s1.nsw.au.coloau.net.au [103.52.116.169] 14 20 ms 21 ms 19 ms vl800-ds1-b5-r1121.aus1.choopa.net [103.43.73.130] 15 * * * Request timed out. 16 21 ms 20 ms 20 ms 176-103-130-130.flops.ru [176.103.130.130] Trace complete. C:\Windows\System32>ping 176.103.130.130 Pinging 176.103.130.130 with 32 bytes of data: Reply from 176.103.130.130: bytes=32 time=19ms TTL=51 Reply from 176.103.130.130: bytes=32 time=20ms TTL=51 Reply from 176.103.130.130: bytes=32 time=19ms TTL=51 Reply from 176.103.130.130: bytes=32 time=20ms TTL=51 Ping statistics for 176.103.130.130: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 19ms, Maximum = 20ms, Average = 19ms Nice, thx avatar.
@Krusty @jimmytim At least you guys are routed to the proper server @Trooper I'll try to come up with a detailed troubleshooting instruction.
Thank you I appreciate it! I should mention that awhile back things were much faster and had a great ping. But for about a month or so now things have been bad and ping times went way up.
Finally, I am back! Here is a bat file which will print routes to all AG DNS servers: https://www.dropbox.com/s/7la0iyn2ufdq8jb/AdguardDNS.bat?dl=0 Could you please try it and pass me the output file?
We got a problem here. So, the route from your ISP to EU server is actually shorter because of the gateways being used. The only solution is for us to add more servers hosted by a different hosting provider. I guess we'll do it eventually, but not right now
Ahh that is a bummer. When I first tried out Adguard DNS beta the ping times were much faster. It seemed to suddenly get slower after you posted awhile back that you had added more servers. Not sure if it is a coincidence or not but it is what it is. Well when you decided to add more servers with a different provider let me know and I will be happy to test. Thank you for looking into this! Cheers!
Tracing route to 176.103.130.130 over a maximum of 30 hops 1 1 ms 1 ms <1 ms 192.168.1.1 2 * * * Request timed out. 3 * 12 ms 12 ms triband-del-59.180.213.33.bol.net.in [59.180.213.33] 4 12 ms 11 ms 12 ms triband-del-59.180.210.209.bol.net.in [59.180.210.209] 5 135 ms 135 ms 136 ms 14.140.210.69.static-Delhi-vsnl.net.in [14.140.210.69] 6 * * * Request timed out. 7 138 ms 130 ms 130 ms ix-ae-0-4.tcore1.MLV-Mumbai.as6453.net [180.87.38.5] 8 147 ms 146 ms 146 ms if-ae-5-2.tcore1.WYN-Marseille.as6453.net [180.87.38.126] 9 145 ms 145 ms 147 ms if-ae-2-2.tcore2.WYN-Marseille.as6453.net [80.231.217.2] 10 146 ms 144 ms 143 ms if-ae-7-2.tcore2.FNM-Frankfurt.as6453.net [80.231.200.78] 11 151 ms 150 ms 150 ms if-ae-4-2.tcore1.FR0-Frankfurt.as6453.net [195.219.87.18] 12 146 ms 147 ms 146 ms 195.219.50.38 13 188 ms 188 ms 188 ms xe000-18.RT.IXC.MSK.RU.retn.net [46.46.128.101] 14 * * * Request timed out. 15 190 ms 188 ms 189 ms 176-103-130-130.flops.ru [176.103.130.130] Trace complete.
This is not a coincidence, for sure. We changed the hosting provider and the new one should be better for most of the people, not for you unfortunately @guest You're being routed to the Russian server. Judging from the trace this is legit, it is the closest to you.
I also had to give up on Adguard DNS for now. There needs to be a way for the user to add exceptions easily. For example, I use the Adguard DNS block list at the router level. The router process the entire block list and also makes it easy to add exceptions if any specific domain is causing problems. See: https://forum.lede-project.org/uplo.../e1796a02a94c107992b2d0bc76d2ea100ec9729e.png * Screenshot is from OpenWrt (LEDE Project) router UI. I am hoping still that Adguard dev team proceeds with a free version and paid version of Adguard DNS and therefore the paid would have more options such as adding exceptions and so on.
DNS is quite a rough and inflexible solution, unfortunately. This is more or less okay for mobile devices, and that's why we made it in the first place, What for exceptions, this is why we will eventually provide AG DNS as an installable package so that you could set it up as you like it.
Love your PC version of AdGuard, Love the DNS servers too, keep up the awesome work, it's companies like yours that I have no issues giving my money to.
g'day is sydney server down? Microsoft Windows [Version 10.0.15063] (c) 2017 Microsoft Corporation. All rights reserved. C:\Windows\System32>ping 176.103.130.130 Pinging 176.103.130.130 with 32 bytes of data: Reply from 176.103.130.130: bytes=32 time=203ms TTL=49 Reply from 176.103.130.130: bytes=32 time=203ms TTL=49 Reply from 176.103.130.130: bytes=32 time=204ms TTL=49 Reply from 176.103.130.130: bytes=32 time=203ms TTL=49 Ping statistics for 176.103.130.130: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 203ms, Maximum = 204ms, Average = 203ms 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 9 ms 8 ms 8 ms 144.130.210.209 4 9 ms 10 ms 9 ms bundle-ether10.exi-core10.melbourne.telstra.net [203.50.11.109] 5 22 ms 21 ms 22 ms bundle-ether12.chw-core10.sydney.telstra.net [203.50.11.124] 6 24 ms 22 ms 31 ms bundle-ether1.oxf-gw11.sydney.telstra.net [203.50.6.93] 7 23 ms 22 ms 22 ms bundle-ether1.sydo-core03.sydney.reach.com [203.50.13.98] 8 23 ms 22 ms 22 ms i-0-1-0-17.sydo-core04.bi.telstraglobal.net [202.84.222.62] 9 160 ms 159 ms 160 ms i-0-4-0-29.1wlt-core02.bx.telstraglobal.net [202.84.136.209] 10 163 ms 161 ms 163 ms i-93.tlot02.bi.telstraglobal.net [202.84.253.86] 11 163 ms 163 ms 162 ms gtt-peer.tlot02.pr.telstraglobal.net [134.159.63.182] 12 203 ms 204 ms 203 ms xe-1-0-0.cr0-sjc2.ip4.gtt.net [89.149.130.254] 13 203 ms 203 ms 204 ms as20473-gw.sjc20.ip4.gtt.net [69.22.130.90] 14 203 ms 203 ms 203 ms vl501-ds1-b5-yd36.sjc1.choopa.net [45.32.142.6] 15 * * * Request timed out. 16 203 ms 204 ms 204 ms 176-103-130-130.flops.ru [176.103.130.130] Trace complete. C:\Windows\System32>
Nope, they're up and running, but you're getting routed to EU. You know, I am starting to think that to fix the routing we simply need to add another set of servers from another provider. We'll do it eventually when there'll be more AG DNS users.
I have tried AG DNS for a while (on my router so that all devices profit from it), but it regularly did not resolve a couple of (Dutch) sites on my iPad (while still resolving others). Weird thing: if I enabled Adguard Pro ("Fake VPN") on my iPad, with the (same?) AG DNS selected, those sites did resolve...
