Oh, I should have read what these tests really do before commenting. So, as you know, DNS requests are chaining. For instance, we use DNS servers of the data center as upstream DNS, they use somebody else's servers and so on. I suppose that somewhere in that chain may be google dns as well. From the privacy point of view it does not mean much as DNS requests sent to the upstream servers do not contain anything identifying you (as these requests are in fact sent by AG DNS and not by you).
Thanks Avatar - I will now start testing since that issue has been explained. (pri) Minimum = 69ms, Maximum = 70ms, Average = 69ms (sec) Minimum = 64ms, Maximum = 65ms, Average = 64ms
I guess, that EU is up and running already, thanks for pointing it out. By the way, it is always better to use secondary server as primary, less people use it.
I did have them reversed inside Acrylic C:\>ping 176.103.130.131 Pinging 176.103.130.131 with 32 bytes of data: Reply from 176.103.130.131: bytes=32 time=67ms TTL=56 Reply from 176.103.130.131: bytes=32 time=67ms TTL=56 Reply from 176.103.130.131: bytes=32 time=67ms TTL=56 Reply from 176.103.130.131: bytes=32 time=67ms TTL=56 Ping statistics for 176.103.130.131: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 67ms, Maximum = 67ms, Average = 67ms C:\>ping 176.103.130.130 Pinging 176.103.130.130 with 32 bytes of data: Reply from 176.103.130.130: bytes=32 time=70ms TTL=55 Reply from 176.103.130.130: bytes=32 time=69ms TTL=55 Reply from 176.103.130.130: bytes=32 time=71ms TTL=55 Reply from 176.103.130.130: bytes=32 time=69ms TTL=55 Ping statistics for 176.103.130.130: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 69ms, Maximum = 71ms, Average = 69ms
So far I am really satisfied, I used Ghostery before and it was unable to block ADs on AStats or naked girls on postimage, AG took care of it. Most webpages do not show ADs or show white space instead, some show failed load, but that is to be expected. I wonder about tracking though.
I was informed this morning that a TV online catch-up player was not working - so I reset the DNS in the router back to OpenDNS, problem solved as it must have been blocking some ad related resource preventing the player to continue. This is not an AG DNS issue of course but the fault of the player forcing ad content. I will continue testing on my pc as I haven`t yet noticed any problems.
It is there for pages blocked as malware/phishing and by parental control (if you use family protection). Ad servers are resolved to the localhost, so there's no blocked page.
@avatar is there a reason my pings are so high? im getting about 180ms. i live in colorado near denver so i wouldnt think the CA servers would be that high.
Is there any difference for the secondary server (.131)? Also it'd be great if you show output of the command "traceroute 176.103.130.130"
No my average ping was 210 ms 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 19 ms 9 ms 9 ms 96.120.12.137 3 9 ms 9 ms 10 ms xe-10-3-2-sur01.denver.co.denver.comcast.net [162.151.38.221] 4 12 ms 9 ms 9 ms ae-20-ar01.denver.co.denver.comcast.net [68.86.128.169] 5 * 19 ms 10 ms lag-16.ear2.Denver1.Level3.net [4.68.63.165] 6 * * * Request timed out. 7 135 ms 135 ms 135 ms RT.AMS.NL.retn.net [213.19.197.66] 8 184 ms 180 ms 180 ms xe000-18.RT.IXC.MSK.RU.retn.net [46.46.128.101] 9 * * * Request timed out. 10 183 ms 182 ms 179 ms 176-103-130-130.flops.ru [176.103.130.130] Trace complete.
That explains everything, for some reason it goes to RU server instead of US. We'll check what's wrong with it, thank you for the trace!
Btw, guys, Adguard DNS now supports DNSCrypt: https://blog.adguard.com/en/adguard-dns-now-supports-dnscrypt/
I have used it for some time, but then it started to timeout too often (several times a day), so I am waiting for it to stabilize. OpenDNS is obviously faster, since it has more servers, but in the end the speed is comparable. Youtube video ADs are blocked, but it causes 5 secs window till the video starts. The main problem is actually the blocking, it is effective, but maybe too much. I could not open some webpages, especially those linked through 3rd party webpages. Lets say, that I would click on Facebook on a link provided by Google leading to Wilders, it would be blocked, because Google ADs are blocked.
No worries. Sorry for delay, it should have been already done, but we couldn't sort things out with the hosting provider.
