-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue: AdGuard DNS servers do have spikes and high latency when testing them via tools like (Smokeping, dnseval, dnsping) #795
Comments
But standard deviation is As I understand, smokeping just uses dig? What if you force TCP there, will it change anything? |
Generally, nothing wrong with dnsping results, it may happen. For instance, when testing cloudflare DNS I see much larger spikes.
And at the same time I don't see any large losses from that place to AG DNS (also Frankfurt), but I am pretty sure if I wait longer I will eventually see some spikes.
A packet got lost and a retransmission was required thus there's a small spike, nothing out of the ordinary. |
I did adopt the smokeping testing to TCPPing (5 pings every 300 seconds). (https://oss.oetiker.ch/smokeping/probe/TCPPing.en.html) These are the results for the last 12h. |
Hi,
after some weeks of testing and comparing I found out, that in general the latency of AdGuard DNS servers is quite good, but it does have many spikes within.
As I do have sometimes longer waiting times for dns responses I started to make some measurements to see whats going on.
When testing via DNSdiag tools for example I do get spikes during testing.
Here some code to test yourself:
(From https://dnsdiag.org/ > install for Linux)
dnsping -c 50 --dnssec --flags -tls -t AAAA -s 94.140.14.49 1.1.1.1
(you can change 1.1.1.1 to some other IP/domain)dnseval --dnssec -t AAAA -f public-servers.txt -c100 -C 1.1.1.1
(public-servers.txt like you want - but you should include 94.140.14.49 and 94.140.14.59 for AdGuard DNS)I think all requests go to german servers in my case.
As you can see from my Smokeping results it shows the same issues (especially during daytime - maybe because of high server load or many users?)
The issues are only there for AdGuard DNS (see am/as > the ratio of average median and average standard deviation)
I used https://oss.oetiker.ch/smokeping/probe/DNS.en.html for the following screenshot and explanation for reading the graphs is here: https://oss.oetiker.ch/smokeping/doc/reading.en.html
The text was updated successfully, but these errors were encountered: